Ask anything. We wrote it down.

A demo is a short polished demo video of your product, up to 90 seconds. You capture the flow, DemoBites writes the script, narrates it, and polishes the video for you in the Editor.

Yes. Sign up with your Google account, or with any email address and a password, from the sign in page.

Yes. Sign up lands on Free, $0: 10 demo minutes a month, a Product Hub with up to 10 published demos, and the In app Pulse. Growth is the whole platform, sized by demo minutes, from $20 a month billed annually for 25 minutes. Full detail on pricing.

A workspace holds everything you make, your demos, your Product Hub, your branding, and your team. Sign up creates one workspace, more in the workspaces docs.

They are example demos every new workspace starts with. You can hide them at any time, hiding never deletes them, and you can restore them later from settings.

Let the Agentic Recorder skill film inside your coding agent, use the native macOS recorder, record a tab with the Chrome extension, or upload a video, all from the create page.

Pick a way to record on the create page, record your flow, then approve the take in your review queue and it becomes a polished, narrated demo. The quick start guide walks you through it.

The agent lane is the Agentic Recorder skill in your coding agent, the manual lanes are the macOS recorder and the Chrome extension, and upload is the last. All of them land in the same polish pipeline, see the create page.

No. Record silently, DemoBites writes the narration from what happens on screen and voices it for you, and you can rescript it or change the voice later in the Editor.

Demos work best at 30 to 45 seconds and 90 seconds is the cap. If your story needs more time, split it into a few short demos instead of compressing one.

By design. Attention on a product demo fades fast, and the demos people watch to the end average about 45 seconds, so the cap keeps every demo inside the span viewers actually give you. A longer story works better as a few short demos.

A full display, a single app window, or a region of your screen, on macOS 14.6 or newer. It is the lane for desktop apps that live outside the browser.

The native recorder is macOS only today, a Windows version is on the way. Meanwhile record a tab with the Chrome extension or upload a video.

Start it from the extension's toolbar button and it films the tab, capturing your real clicks and scrolls along the way. When you stop, the take uploads on its own and lands in your review queue.

It runs in Chrome, Edge and Brave. Whichever you pick, it records browser tabs only.

No, the extension is for browser tabs only. To capture your desktop or another app, use the native macOS recorder.

The extension allows one pending recording at a time, so approve or discard the take that is already waiting before you start another.

The extension records the tab's audio, plus your microphone in narrate mode. The native recorder takes mic on or off at record time. Skill takes have no mic, narration is authored in the Editor.

Yes, upload is one of the ways in. Your video gets AI narration, trimming and chapters, everything except the effects that need live capture data.

MP4, WebM and MOV are supported, up to 2 GB, with MP4 in H.264 recommended for best results.

Auto zoom and smart cursor are built from the capture data our recorders collect while filming, and an uploaded file does not carry that data. Your upload still gets narration, trimming and chapters.

It becomes a regular demo with AI narration, trimming and chapters, and you polish and share it in the Editor like any other demo.

An npx next to your coding agent, Claude Code, Codex or Cursor. Prompt it and it plans a shot list from the live app, clicks through your product in your signed in browser on your machine, and hands the raw take to the Demo agent. It also takes a brief key from GitHub Radar and films every brief, and the demos land in your demo grid.

The knowledge lives in your coding agent, not the skill. Inside your product's repo your agent reads your code and films the right screens, the skill supplies the filming.

Claude Code and Codex get the plugin: add it, run setup, done. The Cursor plugin is not public yet, submitted for review; Cursor and any other agent run npx demobite@latest today. It runs on macOS and Linux with Node 18 or newer.

Add the plugin. In Claude Code: /plugin install demobites --marketplace demobites/agentic-recorder, then /demobites:setup. Setup installs Playwright, ffmpeg and a browser if needed, connects your account with one browser approval and registers the management MCP. Codex has the same plugin; any other agent runs npx demobite@latest once. Full setup lives in the Agentic Recorder docs.

ffmpeg assembles the filmed takes into video, and you no longer install it yourself. Setup, or npx demobite on the one command path, puts a packaged ffmpeg and ffprobe beside the recorder and uses them whenever the system build is missing or too old, and tells you to run it again if neither passes its check.

It is a device link, run by setup or /demobites:login (npx demobite login on the one command path). A short code appears and a DemoBites page opens where you approve in your signed in session and pick a workspace. Your password never touches the terminal, the recorder and your agent never see it.

Nothing gets connected. The agent reports it and stops, and it never retries on its own, the next attempt happens only when you ask for one.

Run /demobites:logout, or npx demobite logout on the one command path, or just ask your agent to log out of DemoBites. That revokes the key on our side and removes it from the machine.

Describe the demo in plain words. Your agent reads the live app's own words, the navigation, headings, buttons and dialogs, and writes a numbered shot list from them with a target length. Your description says what to show, never the words the demo speaks. Nothing films until you say go, then it films in a real browser on your machine, headless by default at 1920 by 1080, and stages the take for your approval in DemoBites, see the Agentic Recorder docs.

The agent opens the browser and waits while you sign in yourself. The skill films in its own browser profile, so your daily browsing never appears in a take, and the session persists, each app asks for a login only once.

The skill retries a silent challenge once with a visible browser, and leaves a verify you are human check to you, one visible window, one attempt. If the site keeps looping it refuses automated filming, so film another flow or record by hand, the recorder never disguises itself.

Yes, you pick the ending. The DemoBites ending, the one the plugin installs, lands the take in the Editor fully editable. A standalone ending that produces a finished MP4 on your machine exists as an advanced manual setup of the skill.

It never presses them. Exports, emails to real people, payments, publishing to a live page and deleting content are pointed at and named on camera. Reversible actions are performed for real and undone after the cut, and Cancel is never a scene.

The recorder key, the footage, the shot list, the narration intent, cursor events and camera targets, all uploaded for processing. Your app session stays in the recorder's own browser profile on your machine, and your password never leaves it.

No. Approving footage makes it a demo in your grid, editable in the Editor. Publishing a version, going live and placing it in your Product Hub each stay separate decisions of yours.

Yes, that is Retake. Ask your agent to retake the demo against what changed, or run /demobites:record retake with the demo's id and a note (npx demobite retake in a plain terminal), and the agent refilms from the saved recipe, keeping your current narration, voice and look while the camera and cuts are refitted. You approve the new recording in the app and the previous one is kept for rollback.

Hand your agent the brief key from GitHub Radar. It lists the briefs from the server, then takes them one at a time behind the scenes: a shot list per brief, filming in your signed in browser, a revert after each cut, and delivery. Since version 1.3.0 a take filmed from a brief becomes a demo by itself, no second review click.

GitHub Radar reads the pull requests you merged on GitHub, drops the bug fixes and writes a brief for every change worth a demo, each under 90 seconds. It never films. Record the briefs yourself with the Chrome extension or the macOS app, or hand them to the Agentic Recorder. The story is on GitHub Radar.

No. GitHub Radar reads merged pull requests and writes briefs, nothing more. Filming is the job of the Agentic Recorder, or yours with the Chrome extension or the macOS app.

The Agentic Recorder is an npx next to your coding agent, Claude Code, Codex or Cursor. Prompt it and it clicks through your product in your signed in browser on your machine, then hands the raw take to the Demo agent. Give it a brief key from GitHub Radar and it films every brief behind the scenes, and the demos land in your demo grid. More on the Agentic Recorder.

No. A prompt is enough: say what to record and it films your product in your signed in browser. GitHub Radar is one way to get briefs, and a brief key is just one more thing you can hand it.

The Demo agent. It takes any raw take from capture through post production: script, narration, zooms, trim, crop, captions, music, intro and outro. The Editor is for the last five percent, small moves. See the Demo agent and [the Editor](/product/editor).

No. GitHub only, read only. Radar starts from a pull request merged into a branch you chose.

A workspace admin goes to Settings, Integrations, GitHub, and installs the DemoBites GitHub App on the repositories you choose. Pick the base branches that count, main by default, leave Comment on merged pull requests on, and set the address where your app runs. Once.

Every pull request merged into one of your base branches after the connection, while the Comment on merged pull requests switch is on. A pull request closed without merging gets nothing.

The DemoBites App, a bot account, posts it on the merged pull request. It carries two actions, Analyze PR and Create demos from this PR.

No. The comment is the entry point and nothing else. A person asks Radar to analyze, approves the briefs and chooses who films them, and publishing, placement and sharing back stay yours.

Yes. For a private repository the person opening the briefs signs in with their own GitHub account once, and without access they see nothing, not even the title. Public repositories need no sign in.

The description, the changed files and their diff, the commit messages and the review comments. Read access only, it never touches your code. That evidence informs the briefs, and no code or diff ever appears in a brief itself.

A short plan for one demo that Radar writes: its title, who it is for, the outcome for the viewer, the flow in a few lines, prerequisites, what to leave out, an estimated length between 15 and 90 seconds, and the evidence it came from. Intent, not a script.

Zero to eight, with the first five ticked by default. Zero is a valid answer, a bug fix or a documentation only change has nothing to demo.

Yes. Edit or reorder any brief, combine two, the page warns past 90 seconds and splits the result, split one, or refine the whole set with a sentence such as only two. Questions the analyzer asked have their own answer boxes.

Approve freezes the briefs you ticked and takes you to the two ways to record them. Nothing is filmed, published or shared at that point, and it stays locked until you have answered the analyzer's questions.

Analysis runs once and coming back lands where you left off. Analyze again appears when the pull request changed, or from the menu, and it is a deliberate second action, not something every visit triggers.

The address of your running product where the change is live, prefilled from the connection and editable per pull request. A merged pull request is not proof that production has it, so point at a staging environment with the right data when needed. Public http or https, no localhost.

Yes, that is the first exit. Record each brief with the Chrome extension or the macOS app, one brief, one demo, and the Demo agent polishes the take like any other. The second exit hands the brief key to the Agentic Recorder.

Copy the brief key from Radar and give it to the Agentic Recorder, the plugin next to Claude Code or Codex (npx demobite for any other agent). It films every brief behind the scenes, one at a time, in your signed in browser on your machine, and each take becomes a demo in your grid. Your credentials stay on your machine.

The other briefs keep going. The failed row says at which stage it stopped and offers Retry. A take the Agentic Recorder is filming on your machine is stopped in your terminal.

Into your grid, unexported, each carrying its source: a From PR #974 badge in the Editor, and the grid search finds them by PR #974 or by words of the title. From there they are demos like any other, and nothing is published or placed on its own.

Yes. When the last brief finishes, the person who approved the briefs gets one email, 2 demos from PR #974 are ready, linking to the grid.

In the app under Create: every pull request with work left and its state, Analyzing, Draft, Approved and waiting for the recorder, Recording 1 of 3, 3 demos ready or Failed, with Continue and Remove. Finished ones sit under Done.

Once at least one demo is live, Share demos on PR #974 posts one grouped comment with a link per demo. The button then reads Shared on PR #974 and sharing again updates that comment. Nothing posts by itself.

No. A demo page has its own page, and that is the link the comment carries. The same link keeps working when you later add the demo to your Product Hub or remove it again.

Yes. Through the DemoBites MCP, hand your coding agent the pull request URL and Radar analyzes it the same way. Ask it to look at the last pull request you shipped and it finds the URL through your git remote first. The MCP lives on Demo Ops.

Every plan, Free included, and the Demo agent and the Editor with them. Demo minutes are the only meter: Free has 10 in total and Growth starts at 25 a month, full detail on pricing.

It is in Takes Waiting for Review. Every recording lands there first and becomes a demo once you approve it.

Yes, every lane lands in Takes Waiting for Review, and a recording becomes a demo only when you approve it.

The take appears in Takes Waiting for Review, ready for you to approve.

The picture, not the words. You see the clean video beside a beat by beat account of what the viewer sees, and since narration is rewritten to fit the video after approval, retake only when the picture itself is wrong.

The take becomes a demo. DemoBites rewrites the narration against what is actually on screen, adds the voice and the camera moves, and opens it fully editable in the Editor.

Discard deletes the staged take, so it cannot be brought back. If an agent filmed it the agent is told, so you adjust and film again.

You never have to record a voiceover. The AI writes a narration script from your recording and speaks it with text to speech. Free has 10,000 text to speech characters in total, and Growth has plenty of text to speech, limited but more than enough.

Click any narration segment in the Editor and edit its text. The audio regenerates in seconds, nothing needs to be recorded again, see the Editor docs.

Pick a different voice in the Editor, voices are organized by language and style, and you can preview any voice before committing. Switching keeps your script.

Yes, on every plan. Connect your own ElevenLabs key and your demos can speak in a cloned or custom brand voice, key setup lives in the Account category.

Add the word to the pronunciation dictionary with a phonetic spelling. Entries apply across your workspace for that language, so every demo says it right.

The Editor detects focus points and adds zooms for you, and every zoom stays editable. Add or move a zoom point on the timeline, then drag the zoom region on the preview.

Cut any section on the Editor timeline to drop dead time or a pause, with an abrupt or fade transition. The Agentic Recorder films tight takes to begin with.

Captions are off by default. Turn them on in the caption panel and they are generated from the narration automatically, no transcription needed.

Yes. Click any caption to edit its text, timing stays in sync automatically, and style, size, and position are adjustable in the caption settings.

Yes. Backgrounds, shadows, corner radius, padding, and an optional browser bar are all adjustable, and your Brand Kit colors and fonts apply to the frame.

Yes. Branded opening and closing frames with your logo are part of the polish, and they render into the export.

Pick a track from the royalty free library and set its volume. It fades in and out automatically and sits under the narration at the level you choose.

No. The built in player previews your demo at any point, and edits to narration, zooms, and captions show up immediately.

Each export creates a new version, and shared links, embeds, your Product Hub, and Pulse all serve the latest version automatically. Nothing you already shared breaks.

Group your demos into folders and label them with tags. Starring a demo pins it to your Product Hub's Latest feed instantly.

Every demo gets a hosted player page with your branding, so you just share its link. Details live in the export docs.

No. Anyone with the link can watch, viewers never need a DemoBites account.

Copy the iframe snippet from the demo's sharing options and paste it into your page. The embed is responsive and keeps its aspect ratio at any width.

A Moment attaches a demo to a word or element on your own site, visitors hover for a preview and click to watch without leaving the page. Open the configurator from the demo card or the Editor, see Moments.

Publish it to your Product Hub, in a release or the Latest feed. Every published demo whose Pulse switch is on also shows in your In app Pulse.

Export the demo from the Editor and download the finished MP4 when the render completes. Exports are unlimited on every plan, with no watermark, and they are never counted.

No. Retake films only the footage again, from the Re-take button on the demo card or in the Editor, or by asking your agent to retake it (/demobites:record retake with the id, npx demobite retake in a plain terminal). Your story, narration and look stay, the camera and cuts are refit to the new take.

It keeps your story, narration, voice, intro, outro, look and links. The footage is refilmed and the camera, cuts and timing are refit to it. The result is a new version that waits for you to publish.

Your public what's new home, hosted by DemoBites. Every release gets a page of its own, smaller updates flow into the rolling Latest feed, and it is all told with demos, see the Product Hub docs.

No. Your Product Hub is public, anyone with the link can browse it and no login is ever asked for.

Every workspace has a public demobites.com address based on its slug, and your Product Hub lives there from the moment you publish. On Growth you can put it on your own domain instead.

Yes. DemoBites publishes its own releases at updates.demobites.com, a real Product Hub, not a mockup.

From the Product Hub section of your dashboard, create a release, give it a title, bring in the demos that show the change, tag it and publish. It goes live immediately, full steps in the publishing guide.

A release is a page of its own with its own URL, shown on the calendar, in search and in tag filters. The Latest feed is a rolling stream for small fixes and tweaks that do not need a dedicated page.

Yes. Releases stay editable after they go live and your changes appear on the same URL when you save. Editing never emails anyone, sending is always a separate action.

Yes to both. A release takes an optional version label, and its date is editable, so you can place it where it truly belongs on your timeline.

Three ways, site search, the tag filters powered by the tags you set on each release, and the release calendar that highlights shipped days.

Open Customize from your Product Hub. Brand colors, fonts and logo come from your Brand Kit, and you shape the header, the content rails and your languages there. Changes go live when you save.

No. Publishing never emails anyone by itself. Release emails go out only when you explicitly send them, so publish as often as you like.

Your public page carries a subscribe box. A visitor enters an email, no account needed, then clicks the link in the confirmation email DemoBites sends, and only confirmed subscribers receive release emails.

Because consent should be provable. Only the click on the confirmation email makes a subscriber, and we stamp the time and source of that consent. Unconfirmed signups expire after 48 hours.

A subscriber is Active, Paused, Unsubscribed, Bounced or Suppressed, and only Active subscribers receive release emails. Details in the subscribers guide.

Yes. Export CSV gives you email, status, consent time, consent source and subscribe time for every subscriber. No IP addresses are stored.

Broadcast sends release emails to your Product Hub subscribers. In the composer you pick the demos, the AI writes the subject and the intro, and you choose a template: Digest, Spotlight or Plain.

Growth. The subscribe form on your Product Hub works on every plan, and emailing your subscribers is Broadcast, which is part of Growth.

Yes. You choose and reorder the updates, pick the lead one, include or drop the Highlight, set the CTA, and regenerate or rewrite any part before sending.

You can send yourself a test copy before the real send. Scheduling is not here yet, a broadcast goes out when you send it.

Yes. Copy HTML puts the exact email markup on your clipboard, ready for your own email tool.

With Localization, an add on, on Growth: $40 a month billed annually, or $50 billed monthly, whatever your demo minutes. It publishes every update in nine languages, English plus eight more, and visitors pick theirs right on the page, see the localization guide.

A new language lands In review. It is published unlisted, so preview links work for anyone you share them with, but visitors do not see it listed until you set it live.

Yes. The pages are public and built for search, sitemaps stay current and pages carry real modification dates, so your whole release history gets indexed.

No. Published pages set no cookies and run no third party trackers, and every published site carries its own privacy page saying exactly what is measured. Whether your jurisdiction wants a banner is your counsel's call.

Yes to both. Switch a release to Inactive and its page comes down everywhere until you reactivate it. Delete removes it permanently after a typed confirmation. A renamed release leaves a permanent redirect, so shared links keep working.

Yes, by design. Every published Product Hub ships llms.txt, markdown mirrors of every page, an OpenAPI surface and its own MCP server, so agents can read your updates with no setup on your side.

llms.txt is the standard index file AI agents look for first when they visit a site. Every published Product Hub includes one automatically, nothing to configure.

Yes. Every page on your published Product Hub has a markdown mirror that agents can read directly, and an OpenAPI surface adds structured access on top.

Every published Product Hub serves its own MCP endpoint at /mcp on your site. Assistants connect with the Model Context Protocol and read your published releases and updates directly.

Your published pages are deliberately open to AI crawlers and answer engines, and there is no per crawler block today.

Yes. With the plugin, setup registers the management MCP right after your account is connected; from any other agent npx demobite mcp does the same and prints the settings. Your agent can then run your whole workspace, demos, releases, languages, highlights, subscribers and analytics, with your approval on anything public. MCP management works on every plan, Free included, detail in Manage from your agent.

More than a hundred tools across nine groups, from demos and releases to languages, highlights, subscribers and analytics. Twenty seven public facing actions pause for your approval, and the full list lives in the MCP tool reference.

Because anything public deserves a human yes. Publishing tools return a preview and a single use confirmation token, your agent shows you the preview, and only your go ahead executes it. Every management call is audit logged.

Yes. In ChatGPT or claude.ai, add a connector pointing at https://app.demobites.com/api/mcp, you approve the connection in your browser, no key to copy. Coding agents like Claude Code and Codex use the plugin, any other agent npx demobite.

Any client that speaks Streamable HTTP with a key or OAuth should connect, those included. We have verified Claude Code and Cursor hands on, and claude.ai and ChatGPT connect through the one URL.

Run /demobites:logout, or npx demobite logout on the one command path, to revoke a terminal key server side, or remove the DemoBites connector in your assistant's settings.

Yes. Every management call is logged, who connected, what was called and what changed, denials included.

In app Pulse is the widget that shows your updates inside your app. A launcher is always visible and counts what is new. A click opens the card, and your users watch there, browse the See all list, or expand a demo into a theatre. It is one widget with no templates, and the launcher is the part you customise.

Every plan, Free included; on Free the widget shows a Powered by DemoBites mark. Feedback, Analytics, Signals and Segmentation in the Pulse are part of Growth.

Rules in the In app Pulse that pin, limit or hide updates by the viewer's role, job or plan, from tags your app sends with the embed. You set them in the Pulse editor, in the Rules and segmentation tab, see Rules and segmentation. Part of Growth.

Copy the embed snippet from your Pulse page and paste it into your app's HTML, there is no build step. It comes in two versions, Quick install and With user tracking, and the full walkthrough is in Embed options.

Every published demo whose Pulse switch is on, automatically. The switch sits on each row of the Library tab in Published demos, and the In-app Pulse tab sets the order. The Pulse lists demos only, never a whole release. The widget shows no demo button, those appear on your Product Hub pages.

Add your domains to the allowed domains list on your Pulse page. The check runs on the server before the widget is served, and an empty list allows every domain.

If you have set an allowed domains list, the widget refuses to load anywhere outside it, and the check happens on the server. With an empty list it loads on any site.

You never redeploy. Publish a demo with its Pulse switch on and the Pulse shows it on its own, the embed snippet in your app never changes.

A Highlight is a short trailer cut from your demos, a 30 to 60 second MP4 built for social posts and launch announcements. Read more in the Highlight docs.

A demo is one polished demo video. A Highlight stitches the best moments from several demos into one short trailer you can post anywhere.

Click Create Highlight in your dashboard, pick a template, then build the highlight in one click or craft it scene by scene in the editor. You need at least 3 published demos, see the Highlight docs.

Yes, every Highlight starts from one of fifteen templates or a Freeform canvas, and the editor controls scenes, titles, music, narration, captions, intro and outro. Browse live demos on the templates page.

Click Render, the render runs in the background and the finished MP4 appears in your render history with a Download button. Details in the editor guide.

Yes. On Free you can preview and export a Highlight. Exports are unlimited on every plan, every demo and Highlight, as often as you like, see pricing.

It shows release membership, that Highlight is attached to a release in your Product Hub.

A Highlight hero is a rendered Highlight used as the lead video of a release page. You add it as an optional step when you create the release in your Product Hub.

Analytics has four tabs: Views & Completion, Product Hub, Pulse and User Feedback. It is part of Growth. On Free it is locked, with a preview on sample data, see the Analytics docs.

No. Tracking is automatic for every published demo, there is nothing to install and no snippet to add.

Every published demo is tracked wherever it plays, on hosted pages, in your Product Hub, in embeds on your own site and through Pulse. Your Product Hub and your Pulse each get a tab of their own.

Views count viewing sessions, conversions count viewers who acted, clicking a CTA or subscribing, and feedback is the helpful and not helpful votes on your updates. See the dashboard docs.

It ranks every demo by sessions and average completion, with each demo shown against your workspace baseline. Click a column to sort, or click a row to drill into that demo's own funnel and retention.

It shows what share of viewers who started a demo reached 25%, 50%, 75% and the end. The biggest drop is highlighted in red, that is usually the moment to fix in the Editor.

It shows what share of viewers is still watching at each point in a demo. A gentle slope means people stay, a cliff marks the moment you lose them.

In the Feedback area of the app, and in the User Feedback tab of Analytics. Both are part of Growth.

Yes. The AI Visibility card shows visitors referred by ChatGPT, Perplexity, Gemini, Copilot and Claude, plus crawler visits with a per bot breakdown.

Signals streams your engagement events to webhook destinations you control, each delivery signed, so activity lands in your own stack in near real time. It is part of Growth.

Events in three groups, Product Hub, subscriber lifecycle and AI crawler visits, chosen per endpoint. The full catalog is in the Destinations docs.

Every delivery is signed with your endpoint secret using HMAC. Compare the signature header to one you compute over the raw body, the recipe and a snippet are in the Destinations docs.

Failed deliveries are retried automatically, 6 attempts over roughly 11 hours, and every delivery is logged so you can replay failures. An endpoint that keeps failing is paused.

The canonical event catalog, payload reference and verification guide live in the Destinations docs.

Feedback asks your viewers one question, Was this helpful?, with a thumb up and a thumb down, and gathers the answers in one place in the app.

On every Product Hub feature page and in the In app Pulse, where the thumbs sit in the card, the player and the theatre.

A thumb down offers five reasons: Too long, Hard to follow, Not what I needed, Something looks wrong and Other. The viewer can also add a note of up to 500 characters, and the note is optional.

It is anonymous by default. It is named when your product passes who is signed in.

In the Feedback area of the app. It has three views, Overview, Notes and By update, and it exports as a CSV.

Growth. On Free, Feedback shows locked, and opening it offers Growth.

Two plans. Free is $0. Growth is sized by demo minutes: a dollar a minute billed monthly, from $25 a month for 25 minutes, or 20 percent off billed annually, from $20 a month. Up to 50,000 unique monthly active users are included. Full details on the pricing page.

Free is a plan of its own at $0, not a trial. You get 10 demo minutes a month, unlimited exports with no watermark, a Product Hub with up to 10 published demos and the In app Pulse, both with a Powered by DemoBites mark. It also has Highlight, up to 1,000 monthly active users and 10,000 text to speech characters in total, for one person, the owner. Editor, GitHub Radar, the Agentic Recorder and MCP are included.

Everything, with the demo minutes you choose, from 25 a month up to 250. That means unlimited published demos, up to 10 teammates per workspace with roles and permissions, Product Hub, In app Pulse, Broadcast, Feedback, Signals, Analytics, Segmentation, plenty of text to speech, unlimited exports, no attribution and a custom domain. Up to 50,000 unique monthly active users are included. The Enablement Center is part of Growth too.

By demo minutes, from 25 a month up to 250, in steps of 25. Billed monthly it is a dollar a minute: 25 minutes is $25 a month. Billed annually you save 20 percent: 25 minutes is $20 a month, paid once a year as $240. Up to 50,000 unique monthly active users are included, see pricing.

A demo minute is a minute of finished demo. Growth starts at 25 minutes a month and goes up in steps of 25 to 250, and you can change the number at any time. Free has 10 minutes a month. Exports are unlimited on both.

Yes, monthly or annually. Billed annually you save 20 percent: 25 demo minutes is $20 a month, paid once a year as $240, and your minutes pool for the whole year. Billed monthly, the same 25 minutes is $25 a month. Localization is $40 a month billed annually, or $50 billed monthly.

A person who interacts with your Product Hub or your In app Pulse during the calendar month. In the Pulse that means opening it or starting a demo. In the Product Hub it means spending at least five seconds on a page, scrolling, clicking, searching, filtering, opening a chapter or subscribing. A page that only loads in a background tab, autoplay and bots do not count. Embedding a demo on your website does not count a monthly active user; only people who actually interact with your Product Hub or Pulse do. Each person counts once a month, whichever of the two they used. Pass your user ids and the count is exact; otherwise people are recognised by a first party id.

Free has 10 demo minutes a month and up to 10 published demos. The 11th demo minute, the 11th published demo and the first teammate invite offer Growth, and so does opening Broadcast, Feedback, Signals, Analytics or Segmentation. Past 1,000 monthly active users nothing is cut, you see an upgrade prompt. Exports are never counted.

Free publishes up to 10 updates in your Product Hub, and the 11th offers Growth. Growth publishes unlimited updates.

Sign up lands on Free, and the app offers Growth when you reach a limit. You pick your demo minutes, and you can change the number later. You pay by card, and the upgrade is immediate and prorated.

Move to Growth. On Free your Product Hub and your In app Pulse carry a Powered by DemoBites mark. Demo exports, Highlight exports and the Highlight preview are clean, with no mark of any kind. Free cannot remove the mark, and on Growth it is gone.

Yes, preview and export. Exports are unlimited on every plan, with no watermark.

Localization is an add on, on Growth: $40 a month billed annually, or $50 billed monthly, whatever number of demo minutes you choose. It publishes every update in nine languages: English plus Spanish, French, German, Portuguese, Japanese, Italian, Dutch and Korean.

Gated access, Personalization, custom contracts, more than 250 demo minutes a month, SAML SSO and unlimited monthly active users. Contact us and Sales sets these up with you.

Paddle, our Merchant of Record. You pay by card, and Paddle handles checkout and tax and sends your receipts and invoices. DemoBites never sees your card details.

Yes, from the billing page in settings. An upgrade to Growth is immediate and prorated. Cancelling returns the workspace to Free at the end of the paid period.

Your workspace returns to Free at the end of the paid period. Cancelling needs 10 or fewer published demos, the Free limit.

Refund terms live in our Refund Policy, and Paddle, our payment processor, issues any refund due.

Open Account and switch to the Profile tab to edit your name, avatar and details.

You can delete your account yourself in the app, confirming the step by typing delete.

The Brand Kit holds your workspace branding, logo, favicon, theme color and fonts. It is picked up from your website automatically, you can edit it in settings, and it is on every plan, Free included.

Add your own ElevenLabs key in settings to use your voices, including cloned ones, alongside the curated set. You can bring your own key on every plan, and it is stored encrypted.

Invite by email, and your teammate is in the moment they sign in. Free is one person, the owner, and the first invite opens Growth. Growth includes up to 10 teammates per workspace, with roles and permissions, at no cost per seat.

Admins can do everything, including billing, settings and managing members. Collaborators work within the section permissions an Admin gives them.

Google sign in works on every plan. SAML SSO is set up through Sales, contact us.

Sign up creates one workspace. On Growth, add as many as you need: each workspace is its own Growth plan, on the same subscription and the same invoice, prorated. Free is one workspace.

On Growth, add a workspace from the app; it is another Growth plan on your existing subscription, one invoice. A workspace gets its primary language, picked once at creation, plus a URL slug and a Brand Kit you can edit later.

Yes. Change the name, the URL slug or both in workspace settings, and every old link redirects to the new address automatically.

It sets the language your recordings are transcribed and voiced in, and the default language of your published pages. You choose it once when you create the workspace.

Yes, on Growth. On Free your Product Hub lives on a demobites.com address.

Growth. See plans and pricing.

No, root domains are not supported. Use a subdomain with at least three labels, for example updates.mycompany.com or demos.mycompany.com.

Add a CNAME record at your DNS provider that points your subdomain to domains.demobites.com, then verify the domain in DemoBites.

Verification does not run on its own, you trigger it. Once your CNAME record is live, open the Custom domain section of your workspace settings and run the verification.

Verification expires after 48 hours. Check that your CNAME record still points to domains.demobites.com, then trigger the verification again from your workspace settings.

Check that the record points exactly to domains.demobites.com, that you are using a subdomain with at least three labels, and that your DNS change has had time to propagate, then run the verification again.

The Enablement Center sits beside your Product Hub: a gated place on our domain where employees, partners and resellers watch briefings behind a magic link, and managers see who watched what. See the Enablement Center docs.

In workspace Settings: turn on the Enablement Center, then Manage who's in. The gate covers only the Enablement Center on our domain; your public Product Hub stays open.

Anyone you assign. Each person gets a magic link and can enter while they are on an active assignment; there is no allowlist.

With a magic link by email, no password. A link lasts 15 minutes with a resend on the sign in page, and the signed in session lasts 7 days.

A demo counts as watched at 95 percent. A person is Ready when every required demo is watched.

Yes, mark a demo Optional in the release studio. Optional viewing shows in the cockpit but never blocks anyone.

Everyone's status, Not started, In progress, Behind or Ready, in three cuts: By person, By demo and the Activity log. The headline number is Completion.

No activity for 5 days shows as Behind. Nudge who's behind when you choose, or let Autopilot repeat it every day, every 3 days or weekly until ship day.

The version turns Shipped, reminders stop, the briefing promotes to the Product Hub, and the record stays for review.

Yes, the By person table exports as a CSV.

Yes. The gate covers only the Enablement Center, and your public Product Hub stays open beside it.

Yes. The Enablement Center is part of Growth, see pricing.

No. It is built for short release communication, not courses or certifications.