Ask your coding agent for a launch video.
One sentence in Claude Code or Codex. Within the hour, a 1080p film with an original score. Your code never leaves your machine.
Invite-only for now. Join the waitlist →
Make a launch video for this app with cutscene.dev
One sentence, three kinds of film.
Same agent, same sign-in, same approval before anything leaves. What changes is where the story comes from: your code, the web, or your deck.
From your repo · 20 s by default
Launch film
Your agent reads your theme, fonts, copy and screens, and Cutscene rebuilds the product in motion. Scored to the cut; a voice-over if you ask.
Ask your agentMake a launch video for this app with cutscene.devFrom a topic or a docs page · 90 s by default
Explainer
Name a concept, or hand over a docs page or a paper. Cutscene does the reading, then animates the ideas step by step, narrated.
Ask your agentMake a 2-minute explainer of how LoRA fine-tuning works with cutscene.devFrom your deck or your repo · 45 s by default
Pitch film
For investors and partners: the problem, the product and the ask, in your brand, narrated. Your agent pulls the story from your slides.
Ask your agentMake a 60-second pitch film from our seed deck with cutscene.dev
Made with Cutscene.
Real films from the beta: explainers of a topic or a docs page, launch films briefed from repos, pitch films for investors and clients. Every frame is rendered from code, with a score written for it.
GPU kernels, for web developers
What it takes to make one LLM operation run faster than a production inference engine, explained for people who build for the web. Version 3: revised twice from notes.
Then keep changing it.
Every film keeps its project. Tell your agent what to change, in plain words, and the next version is made from the same scenes: only what you asked for moves. Each version keeps its own page.
- v1
YouMake a launch video for this app
The first cut: five scenes, scored to the beat.
- v2
YouHold the dashboard longer and make the end card orange
Ready in minutes. The dashboard scene and the end card changed; nothing else did.
- v3
YouChange the headline to “Ship with confidence”
One headline changed. Same timing, same music.
Hold the dashboard longer and make the end card orangeHow a film gets made.
Your agent does the briefing, because it already knows your app. Cutscene only ever sees the answers you approve.
- 01
You ask.
In Claude Code or Codex, in plain words. No install, no keys: your agent reads cutscene.dev and knows what to do.
- 02
You sign in once.
A browser tab opens. Type your email and the 6-digit code we send. Your agent keeps the sign-in for next time.
- 03
Cutscene asks back.
Fifteen questions come back, each with a hint about where in a repo its answer usually lives. An explainer needs only the topic.
- 04
Your agent answers from your code.
On your machine, it reads your theme, fonts, landing copy and key screens, and writes down facts: hex values, font names, a one-line pitch.
- 05
You approve what leaves.
Every answer and every file, shown once. Strike anything. Only this package crosses: no source, no config, no .env.
- 06
Cutscene makes the film.
In an isolated sandbox a director picks a concept and a tempo, builds each scene in React, scores it to the cuts and checks every frame. If every sandbox is busy, yours waits its turn.
- 07
Your film arrives.
Within the hour: an email, and a private page with the 1080p film. Flip one switch to share it, or ask your agent for changes.
Illustrated with the vizz.fm launch film. The colors, fonts, pitch and scenes are from its brief.
What leaves your machine.
Your agent is the only one that reads your code. You see the package before it goes.
Sent, after you approve
- A one-line pitch and 3–5 shipped features (or, for an explainer, just the topic)
- Brand colors as hex values, font names
- Your logo file
- Screenshots you approve, with demo data
- Plain-language descriptions of key screens
- The call to action and a public URL
Never sent
- Source code — not a file, not an excerpt
- Config, lockfiles, .env files, keys
- Customer data or database contents
- Internal URLs, git history, issues
- Anything you strike from the package
The fifteen questions, and where your agent looks for each answer
| # | Question | Looks in |
|---|---|---|
| 01 | What kind of video: launch (default), pitch or explainer?optional | ask the user |
| 02 | Explainers only: docs, specs or papers to start research from.optional | ask the user, or links they shared |
| 03 | In one sentence: what does the product do, and for whom? For an explainer: the topic, and for whom. | README, landing page hero copy, package description |
| 04 | 3–5 headline messages or features (explainers: the concepts, in order). Only things that are real and shipped today. | landing page sections, feature flags that are on, changelog |
| 05 | Who is the audience and what tone fits?optional | landing copy voice, marketing pages |
| 06 | Voice-over: the voice you want, or none. Pitch films and explainers are narrated by default.optional | ask the user |
| 07 | Brand colors as hex with roles. Dark or light product? | tailwind config, CSS variables, theme tokens |
| 08 | Font families for headings, body and code. | next/font or @font-face, tailwind fontFamily |
| 09 | The logo — SVG preferred, plus a light-on-dark variant if one exists.optional | public/, assets/, app/icon.* |
| 10 | 2–5 screenshots of the key screens, with demo data.optional | run the app locally, or existing marketing shots |
| 11 | Layout, components and labels of each key screen — described, not pasted.optional | the page and component files for those screens |
| 12 | End-card call to action and URL. | primary button, deployment domain |
| 13 | Anything the video must not claim or show.optional | ask the user |
| 14 | Length in seconds (10–180; default 20 launch, 45 pitch, 90 explainer).optional | ask the user |
| 15 | Studio (about 45–60 minutes, reviews its own frames) or quick (about 20–30 minutes).optional | ask the user |
Built to be called, not clicked.
Cutscene is a remote MCP server with an agent skill on top. Every page here also answers in Markdown.
endpointhttps://cutscene.dev/mcp
transportstreamable HTTP · stateless · OAuth sign-in
toolcreate_video(product_name, brief, product_url?) — Opens a job and returns the questionnaire.
toolupload_url(job_id, question_id, filename) — A one-off signed URL (30 min) and a ready curl command for a logo or screenshot.
toolsubmit_answers(job_id, answers) — Saves text answers; reports what's still missing.
toolstart_video(job_id) — Queues the render once every required answer is in; it starts when a sandbox is free. Also retries a failed job.
toolget_status(job_id) — Progress while rendering; the video URL, report and usage when done.
toolrevise_video(job_id, notes) — The next version of a finished film from its own project: only what the notes ask for changes.
Private beta.
Cutscene is invite-only while we tune the director, and films are free for invited people during the beta. Once you’re in, it’s one sentence to your agent and a one-time sign-in with your email.
Join the waitlistMake a launch video for this app with cutscene.devNo keys or tokens to copy. How sign-in works →