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 Demo Studio.

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

Yes, Starter needs no credit card: every recorder on your machine, the Studio, 25 minutes of exports a month, and 25 demo pages on your own domain in an Update Center and Explore Center, no watermark, with a small DemoBites attribution on the pages. Grow is $250 a month ($200 a month billed yearly) with 250 demo pages, no attribution, unlimited exports, Spotlight, analytics, Retake, Pulse, Broadcast, Signals, the Cloud Recorder and Workflows from GitHub; Scale is per contract, full detail on pricing.

A workspace holds everything you make, your demos, your centers, your branding, and your team. Switch between them from the switcher at the top of the sidebar, 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.

Record in the cloud, 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 one of the five ways 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.

Agent lanes are the cloud recorder and the coding agent skill, manual lanes are the macOS recorder and the Chrome extension, and upload is the fifth. All five 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 Demo Studio.

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, use the cloud recorder, 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. Cloud and skill takes have no mic, narration is authored in Demo Studio.

Yes, upload is one of the five lanes. 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 Demo Studio like any other demo.

An agent that films your product for you. Describe the demo, or hand it the briefs of a workflow, and it plans a shot list from the live app, films a real browser and delivers an editable demo, as a skill in your coding agent or as the cloud recorder on our machines.

If you work in a coding agent like Claude Code or Cursor, use the skill. Your machine, your sessions, and your agent knows your codebase, fewer wrong turns on film. Not in a terminal, use the cloud recorder, nothing to install, and it works for anyone on the team.

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. The cloud recorder plans by walking your live site.

Claude Code is the installed target: npx demobite puts the skill in place for it. Codex and Cursor run it too once you point them at the skill file and let them run its scripts. It runs on macOS and Linux with Node 18 or newer.

Run npx demobite@latest once in your project. It installs the skill, sets up Playwright, ffmpeg and ffprobe beside it, and registers the DemoBites management MCP with Claude Code when the project is already connected. Run it again to update the skill. Full setup lives in the Agentic Recorder docs.

ffmpeg assembles the filmed takes into video, and you no longer install it yourself. npx demobite puts a packaged ffmpeg and ffprobe beside the skill 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. The terminal prints a short code and opens a DemoBites page where you approve in your signed in session and pick a workspace. Your password never touches the terminal, the skill 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 npx demobite logout, 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 npx demobite installs, lands the take in Demo Studio 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 Demo Studio. Publishing a version, going live and placing it in a Center each stay separate decisions of yours.

Yes, that is Retake. Run npx demobite retake with the demo's id and a note on what changed, 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. Retake comes with Grow and Scale, see Retake.

Paste the recording prompt from the workflow into your agent. It lists the briefs from the server, and says so if your paste drifted, then takes them one at a time: a shot list per brief, one word from you, filming, 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. Recording briefs from a pull request needs Grow or Scale, describing a demo in plain words stays on every plan.

The same recorder running on our machines, nothing to install and no terminal. You give one domain and one prompt, approve the storyboard, and we film it, details in the cloud recorder docs.

A planner walks your site and photographs a storyboard, the full plan arrives in about a minute. After approval filming takes a few minutes, and an email links you to the take in your review queue.

Recording on your own machine is free on every plan, Starter included. Cloud recording behind a login is part of Grow and Scale.

Public recording is included on every plan, so it is the preselected choice. Switch it when your demo needs a login, signed in recording is part of Grow and Scale.

Grow and Scale. Any signed in cloud recording, whether a fresh sign in or a saved one, is part of Grow, while the recorders on your own machine are free on every plan.

You sign in yourself in a real browser window, and your password goes to the app you are signing in to, never to DemoBites. What we keep is the resulting browser session, encrypted and revocable by you.

Yes. Saved logins are kept per app, each encrypted with its own key, and reusable across runs on Grow and Scale. Revoking one wipes it for good.

Yes. Recording with a second profile or persona is available on Grow and Scale.

Yes. The approval page shows a real screenshot per step with a movable zoom box and the narration beside it. Approving films it verbatim, and leaving notes sends the plan back for a rework before filming.

No, it films websites and web apps only. Desktop capture is the native macOS recorder's job.

One recording per run, websites and web apps only, and inside a workflow one job per brief. Demos work best at 30 to 45 seconds with a hard cap of 90 seconds. Recording is not metered, exporting uses your plan's export minutes, see pricing.

A workflow turns a shipped change into demos without leaving the tool it shipped in. A pull request merges or a Jira issue moves to Done, DemoBites reads the change and suggests short briefs, you approve them, an agent records them, the finished demos land in your grid, and one click posts them back on the same item. The story is on Workflows.

GitHub and Jira, and you can connect both. GitHub starts on a merge into a branch you chose, Jira on an issue moving to Done in a project you watch. More integrations are on the way.

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.

A workspace admin goes to Settings, Integrations, Jira, and connects through the Atlassian consent screen. Pick the site, the projects to watch, leave Comment on issues moved to Done on, and set the address where your app runs. Disconnecting removes the webhooks.

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.

An issue in a watched project that moves into any status of the Done category. It gets one comment, once. Other transitions post nothing.

On GitHub the DemoBites App, a bot account, posts: Turn this change into a product demo. Create demos from this PR. On Jira the same comment reads Create demos from this issue, posted as the person who connected Jira.

No. It creates the entry point and nothing else. A person starts the analysis, approves the briefs and chooses how to record, and publishing, placement and sharing back stay yours.

Yes. For a private repository the person opening the workflow 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. That evidence informs the briefs, and no code or diff ever appears in a brief itself.

The summary, description, comments, labels, components, fix versions, linked issues and status history. Not the epic's children, attachments or linked pull requests, so a thin issue can yield zero briefs.

A short plan for one demo: 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 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 recording. 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 or the issue 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 workflow. 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.

Copy the recording prompt or download the briefs, paste them into Claude Code, Codex or Cursor with the DemoBites skill installed by npx demobite, and your agent takes one brief at a time: it plans a shot list from the live app, films on your word, uploads the take, and it becomes a demo by itself. Your credentials stay on your machine.

DemoBites films the briefs on its own machines, one job per brief in order. If the app needs a login you sign in once in a live window and the session is kept in your vault, never the password. Review each plan before filming or let it run, and each finished job becomes a demo by itself. Cloud recording is part of Grow.

The other briefs keep going. The failed row says at which stage it stopped and offers Retry on either path. A cloud job still queued or planning can be cancelled from the page, a job already filming cannot, and a take running on your machine is stopped in your terminal.

Into your grid, unexported, each carrying its source: a From PR #974 badge in Demo Studio, 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.

Under Create, Workflows: every workflow 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 workflows 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. On Jira the same reads Share demos on ABC-123. 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 Update Center or remove it again.

Yes. Through the DemoBites MCP, hand your agent the pull request URL, or the issue key on Jira, and it opens the same workflow. Ask it to look at the last pull request you shipped and it finds the URL through your git remote first.

Connecting GitHub or Jira and the comment on the item are open to every plan. The first Analyze is the door to Grow and Scale, Record in the cloud comes with Grow, and your plan's demo pages cap meters the outcome, 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, all five lanes land in Takes Waiting for Review, and a recording becomes a demo only when you approve it.

The take appears in Takes Waiting for Review, and a finished cloud recording also emails you a link straight to the take.

Yes, runs still in flight show live status in the review queue, and if one fails you see the actual reason.

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 Demo Studio.

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.

No, takes are never rejected. The plan limit applies only when a take becomes a demo, so it simply waits in the queue until a slot frees up or your plan grows.

You never have to record a voiceover. The AI writes a narration script from your recording and speaks it with text to speech, which is included.

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

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

Yes. 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 Studio 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 Demo Studio timeline to drop dead time or a pause, with an abrupt or fade transition. The agent lanes film 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 centers, 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 Update Center'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 Studio, see Moments.

Publish it to your Update Center, in a release or the Latest feed, or to your Explore Center. Demos in docked releases also appear in your Pulse widget.

Export the demo from the Studio and download the finished MP4 when the render completes. Exports carry no watermark on any plan. Starter generates up to 25 minutes of exports a month, and Grow and Scale are unlimited, any length. Downloading the original recording or an export you already made never counts.

No. Retake films only the footage again, from the Re-take button on the demo card or in Demo Studio, or with npx demobite retake in the 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.

Grow and Scale, enforced on every way in, the button, the terminal and queued retakes alike.

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 Update Center docs.

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

Every workspace has a public URL based on its slug, and your Update Center lives there from the moment you publish. On every plan, Starter included, you can put it on your own domain instead; Starter keeps a small Powered by DemoBites label, Grow and Scale remove it.

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

From the Update Center 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.

Docking puts a release into your Pulse widget. Pulse is a replica of your Update Center inside your app and shows docked releases only, so docking decides what your users see there.

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 Update Center. 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 turns a release into a finished branded email. The AI writes it from what is already in the release, your title, summary, demos and Brand Kit, and you review it and send it to your subscribers.

Subscribers and Broadcast release emails come with Grow and Scale.

Yes. You choose and reorder the updates, pick the lead one, include or drop the Spotlight, 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.

Localization is an add on, $150 a month on Grow ($120 a month billed yearly), included on Scale. You can publish in up to 8 languages beyond your primary one 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.

Your public evergreen demo playlist, the place you send prospects who want to see the product first. It plays your polished demos as one lineup and gives each demo its own page, see the Explore Center docs.

The Explore Center sits before signup and proves the product to prospects, the Update Center sits after signup and shows customers everything you keep shipping. They are companion public surfaces of the same workspace.

Short polished demos, roughly a minute each, one capability per video, covering the flagship capabilities of your product.

An Explore Center holds up to 8 demos, so curate the lineup to your strongest capabilities.

You pick the demos and set their order from the Explore Center in your dashboard. Order matters, play all runs the lineup exactly as you arranged it.

Yes. Every demo in the playlist also gets a page of its own with a shareable link, so you can send someone straight to the exact video instead of the top of the playlist.

Pick one of the four templates and your Brand Kit colors, fonts and logo are applied automatically. There is nothing to design by hand.

Build your playlist, pick a template, and publish from the Explore Center in your dashboard. You can pause it later whenever you want.

Yes. Every plan has an Explore Center, Starter included, where you create, customize, publish and pause it, on your own domain. On Starter it carries a small DemoBites attribution; Grow and Scale serve it with none. Extra languages come with the Localization add on.

They are sibling centers, and each one links to the other automatically. The sibling link shows in every language your center is published in.

The sibling link always shows, and when your Explore Center does not have Spanish it falls back to its default language center. Once your Explore Center is available in Spanish, the link opens in Spanish.

Yes. Your Explore Center keeps its own language list, separate from the Update Center's, managed in its customize studio under Languages. Adding languages is part of the Localization add on.

When a flow changes, record a fresh demo and swap it into the playlist. Your analytics show which demos get watched and which get skipped, so you know what to replace or reorder.

Yes, by design. Every published Update Center 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 Update Center includes one automatically, nothing to configure.

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

Every published Update Center 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. One exception: Free workspaces without a custom domain are not indexed.

Yes. Run npx demobite mcp, it wires Claude Code directly and prints the setup for any other agent. Your agent can then run your whole workspace, demos, releases, languages, spotlights, subscribers and analytics, with your approval on anything public. MCP management works on every tier, Free included, detail in Manage from your agent.

More than a hundred tools across nine groups, from demos and releases to languages, spotlights, 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 Cursor use npx demobite instead.

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 npx demobite logout 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.

Pulse is the What's New widget that lives inside your app. It is a replica of your Update Center, so your users see the releases you have docked without leaving your product.

Pulse is available on Grow and Scale.

Copy the embed snippet from your Pulse page and paste it into your app's HTML, there is no build step. The full walkthrough is in Embed options.

Docked releases from your Update Center, nothing else. The widget is a replica of your Update Center, and docking itself is explained in the Update Center category.

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. Pulse mirrors your Update Center, so manage your docked releases there and the live widget follows, the embed snippet in your app never changes.

A Spotlight 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 Spotlight docs.

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

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

Yes, every Spotlight 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.

Upgrade to Grow. Spotlight is part of Grow and Scale, and exports with no watermark, see pricing.

It shows release membership, that Spotlight is attached to a release in your Update Center.

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

Analytics shows views, conversions and feedback, plus a demo leaderboard, a completion funnel and retention curves. It is included on Grow and Scale, 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 Update Center and Explore Center, in embeds on your own site and through Pulse. Both centers also get dashboards 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 Demo Studio.

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.

Each update on your public page collects helpful and not helpful votes, and on Grow and Scale the results appear in the Update Center analytics dashboard.

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

Destinations streams your engagement events to webhook endpoints you control, so activity lands in your own stack in near real time. It is included on Grow and Scale.

26 events in four groups, Update Center, Explore Center, 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.

Three plans. Starter is free: it makes the videos and publishes 25 demo pages on your own domain. Grow is $250 a month, or $200 a month billed yearly, with 250 demo pages and everything that reaches customers: Spotlight, analytics, Retake, Pulse, Broadcast, Signals, the Cloud Recorder and Workflows from GitHub. Scale is per contract with no limit. The Enablement Center ($100) and Localization ($150) are add ons on Grow, and annual billing takes 20 percent off everything. Full details on the pricing page.

Starter is a permanent plan, not a trial, and needs no credit card. You get every recorder on your machine, the Studio with unlimited demo projects, text to speech in every voice, 25 minutes of Full HD exports a month with no watermark, one workspace for one teammate, and up to 25 demo pages in an Update Center and Explore Center on your own domain, with a small Powered by DemoBites attribution.

Yes. Starter never expires, exports are watermark free within 25 minutes a month, and your 25 demo pages stay published on your own domain, with the DemoBites attribution. What it does not do is reach: no attribution, Spotlight, analytics, Retake, Pulse, Broadcast, Signals, the Cloud Recorder and Workflows from GitHub start on Grow, so it is reach you outgrow, not time.

Nobody picks a count up front. Starter publishes 25, Grow 250 and Scale has no limit. On Grow, at the 251st demo page the app offers 25 more for $25 a month with one click, as many times as you like, and you remove a pack in Manage plan. Starter has no packs: its 26th demo page is the door to Grow.

At the 26th demo page, past 25 minutes of exports in a month, or the moment you want your pages without the DemoBites attribution, Spotlight, analytics, Retake, Pulse, Broadcast, Signals, the Cloud Recorder or Workflows from GitHub. Grow is $250 a month, or $200 a month billed yearly, with 250 demo pages.

Grow, $250 a month or $200 a month billed yearly: 250 demo pages with packs of 25 beyond, unlimited teammates, workspaces and exports, no DemoBites attribution on your pages, Spotlight, analytics, Retake, Pulse, Broadcast emails and subscribers, Signals into your own backend, the Cloud Recorder with logins and proxies, Workflows from GitHub pull requests, plus the two add ons. Everything in Starter is included: your own domain, no watermark, Update Center, Explore Center, unlimited workspaces, MCP and the recorders on your machine.

On Grow, yes: at the 251st demo page the app offers 25 more for $25 a month ($20 on annual billing), one click, as many times as you like, and packs come off in Manage plan. Starter is fixed at 25; its 26th demo page is the door to Grow. Scale is unlimited.

Scale has no demo page limit and includes both add ons; talk to us about a plan sized to your catalog.

Every demo in your workspaces counts toward the limit, drafts included. Failed imports and the built in examples never count. At the limit, unpublish a demo, move up from Free, or talk to us about an Enterprise agreement.

Move to Grow. Starter serves your pages and Centers on your own domain with a small Powered by DemoBites label; Grow and Scale remove it. Exported videos never carry a watermark on any plan.

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

Yes. You can upgrade, downgrade, change your demo page count or switch an add on on or off at any time from the billing page in settings.

You keep everything. Demos over the lower limit are locked, not deleted, and they are waiting for you if you upgrade again.

Your plan runs to the end of the billing period, then the workspace moves to Free with its 8 demo limit. Demos over the limit are locked, not deleted.

Yes. Grow, the packs and both add ons are 20 percent off billed yearly: Grow $2,400 a year, packs $240, Localization $1,440, the Enablement Center $960. Flip the Monthly / Annual toggle on pricing. Scale is per contract.

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 and you can edit it in settings.

Add your own ElevenLabs key in settings to use your voices, including cloned ones, alongside the curated set. The key is stored encrypted.

Invite by email, and your teammate is in the moment they sign in. Starter is a single seat; from Grow up seats are unlimited and free. Admin and Collaborator roles cover most teams, granular per member permissions come with Scale.

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. For SAML SSO, talk to us about the Custom plan.

One on Starter, unlimited on Grow and Scale, one per product or brand.

Open the workspace switcher at the top of the sidebar and choose Create Workspace. You pick the primary language once at creation, and a URL slug and a Brand Kit are set up for you, all editable 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 every plan, Starter included, you serve your Update Center and your Explore Center from your own domain.

Every plan, Starter included. 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.

Yes. Each surface has its own slot, an Update Center domain and an Explore Center domain, so you can point a separate subdomain at each.

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 is the third center beside your Update Center and Explore Center: 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 centers stay open.

Anyone you assign. Each person gets a magic link and can enter while they are on an active assignment; there is no allowlist. The add on covers up to 100 unique participants across active assignments, and closing an assignment frees seats.

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 Update Center, and the record stays for review.

Yes, the By person table exports as a CSV.

Yes. Run a public workspace for your customer facing Centers beside the private one, under the same account.

Yes. The Enablement Center is a $100 a month add on on Grow ($80 a month billed yearly), covering up to 100 unique viewers across active assignments, closing an assignment frees seats. Included on Scale, see pricing. For more viewers, [book a walkthrough](/book-demo).

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