# Chapter Demos: AI product demo videos, filmed in your real app

> AI demo videos of your web app, filmed from your code. No screen recording, and they stay current as you ship. Your first 3 demos are free.

Markdown of https://chapter.dev/demos, for AI agents. The whole site in one file: https://chapter.dev/llms-full.txt

[NewOur product demo agent toolkit is now open source. View on GitHub](https://github.com/chapter-dev-pty-ltd/product-demo-agent-toolkit)

# Create videos of your product that customers love, using AI

Connect your GitHub repo or your staging site, describe the video, and Chapter’s AI agents film it in your real product. No screen recording, and it stays current as you ship.

Chapter is opening from a waitlist. Join it with an email address in the form on this page, and Chapter emails you when your invite is ready.

Or [book a demo](https://calendar.app.google/Yj4xjVGF1nhk2WLV9) and we’ll set up your app with you.

Use cases

## For every team that shows your product.

-   [

    ### Changelogs

    Assets created for every change. Automatically.

    ](https://chapter.dev/use-cases/changelog-videos)
-   [

    ### Support

    Self-service support demos for every customer.

    ](https://chapter.dev/use-cases/help-centre-videos)
-   [

    ### Product marketing

    Create launch assets on demand.

    ](https://chapter.dev/use-cases/launch-videos)
-   [

    ### Sales

    Demos set in each prospect’s own world.

    ](https://chapter.dev/use-cases/sales-demo-videos)

## Videos and photos, finished.

-   **Your real product.** An agent films it, with voiceover and captions.

-   **Current as you ship.** Every asset keeps up with your product’s changes.

-   **Changed in plain words.** Ask for different data, branding, voice or style.

Filmed by Chapter

## Real products, filmed from their code.

### Plane: Planning a sprint

Filmed from Plane’s open-source code. Plane isn’t a Chapter customer.

-   [Plane: Planning a sprint](https://chapter.dev/samples/plane.mp4) (Filmed from Plane’s open-source code. Plane isn’t a Chapter customer.)
-   [Documenso: Sending a contract for signature](https://chapter.dev/samples/documenso.mp4) (Filmed from Documenso’s open-source code. Documenso isn’t a Chapter customer.)
-   [Infisical: Adding a secret to two environments](https://chapter.dev/samples/infisical.mp4) (Filmed from Infisical’s open-source code. Infisical isn’t a Chapter customer.)
-   [Papermark: Sharing a document behind a password](https://chapter.dev/samples/papermark.mp4) (Filmed from Papermark’s open-source code. Papermark isn’t a Chapter customer.)
-   [Rallly: Booking the best date for a meeting](https://chapter.dev/samples/rallly.mp4) (Filmed from Rallly’s open-source code. Rallly isn’t a Chapter customer.)

NewOpen source · 17 November 2026

## We’ve open‑sourced our demo toolkit.

The product demo agent toolkit lets Claude Code, or any coding agent, film your web app on your own machine. It explores the app, writes the film, rehearses it, shoots it in a real browser and cuts an mp4, with a drawn cursor, click and typing sounds, highlights and an optional voiceover. MIT licensed.

[View on GitHub](https://github.com/chapter-dev-pty-ltd/product-demo-agent-toolkit)

Rather not run it yourself? Chapter does it for you, from your repo.

```
# learn the app
product-demo-agent-toolkit explore http://localhost:3000
# a full run, a still after each step
product-demo-agent-toolkit rehearse film.json
# the same run, filmed
product-demo-agent-toolkit shoot film.json
# the mp4
product-demo-agent-toolkit cut
```

## Questions teams ask before they pick a tool.

-   ### Is Chapter right for our product?

    If your product is a web app, yes. Connect your GitHub repo, or give Chapter your staging site’s address and a test login if you’d rather not share code. Monorepos work, and so do Electron apps.

    From your code, Chapter fills the app with a world you choose and films branches and pull requests before they ship. From a staging site, it films the site as it is, with your test data, and you can connect GitHub later for worlds and pull request demos. It isn’t for native mobile apps.

-   ### What will be on screen?

    A world you choose. Chapter fills its copy of your app with realistic data: customers, records and media, so every list is full and every screen looks lived in. Make a named dataset per customer or industry, from a short brief. From your code, real customer data never appears, because Chapter never logs in to your product. From a staging site, it shows the test data your staging site holds.

-   ### Will it work on a complex app?

    Usually, yes. Chapter builds your real frontend from its source, so every screen is your own code, not a recreation. Your backend is replaced with stand-ins that keep what happens: sign in, create a record, move it through a workflow, and the next screen shows the change. Integrations such as payments, email and file uploads are answered the same way.

    Setup isn’t finished until Chapter has done your product’s main flows end to end in a real browser, repairing what fails along the way. The films of Plane, Documenso, Infisical, Papermark and Rallly on this page were each made this way from their open-source code.

    The limit: stand-ins follow what your code shows the backend doing, they don’t run your server. If a screen depends on heavy server-side logic, like a pricing engine, film your staging site instead, which shows the real thing.

-   ### What happens when our product changes?

    The videos keep up. Chapter’s copy of your app follows your code and repairs itself on each build, so a demo can be remade of what’s live now just by asking. A daily check of what you merge lists the features you shipped, ready to turn into changelog videos.

-   ### Can it film something that hasn’t shipped yet?

    Yes. Chapter films a branch or pull request, so the launch video is ready before the launch. On each pull request it comments with the photos and videos it plans to make of the change, and a “/chapter” comment asks for more.

-   ### What can we make with it?

    -   Launch videos that tell the story of a new feature.
    -   Short changelog updates for every release.
    -   Help-centre how-tos and onboarding walkthroughs.
    -   Sales demos set in each prospect’s own kind of data.
    -   Product photos for your site, docs and socials.

    Every video is finished: framed, captioned, with an AI voiceover and music, in a visual style you pick.

-   ### Who makes the videos?

    Anyone. Engineering connects the repo once; after that marketing, product, sales and support ask for videos in plain words, in Chapter, in Slack, or from Claude, Codex or any MCP client. There is no recording, timeline or test account to manage. Each request gets several takes, and any video can be shared as a watch page, password protected if you like, with views and comments.

-   ### How do edits work?

    Ask for them in words: “trim the intro”, “hold on the chart”, “use a dental clinic’s data”. Trims, holds and line changes recut in seconds. A change to what happens on screen refilms only the steps that changed, so one scene can be fixed without touching the rest.

-   ### Is our code safe?

    Chapter reads your repository with read-only GitHub access and builds it in an isolated cloud sandbox. Your backend and integrations are replaced with stand-ins that answer from generated data, so Chapter never touches your production systems, your databases or your customers’ data. A staging site’s test login is stored encrypted and typed only on your own site.

-   ### How is Chapter different from Clueso, Demosmith or Arcade?

    **Clueso and ngram** polish what you give them: screen recordings, documents and release notes. Chapter needs no recording. It runs your product from its code, films it in your buyer’s world, and refilms it when the code changes.

    **Demosmith** drives your live site from a URL and a login, so every demo shows the same test account and only what’s deployed. Chapter can film your staging site the same way, and from your code it also fills the app with a world you choose for each prospect, including features not shipped yet.

    **Arcade and Supademo** capture screens you click through. Chapter films finished videos and photos with nobody clicking, set in each buyer’s world.

    **Demostack** builds clickable environments for reps to run live. Chapter makes finished videos and photos, refilmed in each prospect’s own world.

-   ### What doesn’t Chapter do?

    It doesn’t film native mobile apps, and it makes videos and photos rather than clickable demos a buyer drives themselves.

-   ### How do we start?

    [Join the waitlist](https://chapter.dev/demos#join) and we’ll email you when your invite is ready. Then connect your GitHub repo. If you’d like a hand, [book a demo](https://calendar.app.google/Yj4xjVGF1nhk2WLV9) and we’ll set up your app with you. Rather not share code? Book a demo and we’ll set Chapter up on your staging site.

## See your own product filmed.

Or [book a demo](https://calendar.app.google/Yj4xjVGF1nhk2WLV9) and we’ll set up your app with you.

[Chapter](https://chapter.dev/)

Product

[Demos](https://chapter.dev/demos) · [For agents](https://chapter.dev/agents) · [Compare tools](https://chapter.dev/compare) · [Open source toolkit](https://github.com/chapter-dev-pty-ltd/product-demo-agent-toolkit) · [Join the waitlist](https://chapter.dev/demos#join)

Company

[Contact](https://chapter.dev/contact)

Legal

[Privacy](https://chapter.dev/privacy) · [Terms](https://chapter.dev/terms)

© 2026 Chapter
