Fluxcut
Start

WHAT FLUXCUT IS

The product demo
companion
for teams and agents

Fluxcut makes demo videos for your product.
You describe the product then Fluxcut makes the video with or for you.

Connect your agent
See how it works ↓
Kept in stepSame lengthBriefWhat it arguesFootageYou uploadTimelineShots + secondsScriptA line per shotVoiceoverA take per lineMusicTo the secondThumbnailYou pick oneFinal videoPicture + soundSoft PublishWhen you say
Planned with youMade by FluxcutRendered, the same every timeKept in step

Hover a word to see what it means

COPILOT OR AGENT

You Make it with Fluxcut or Let Agents Do it

Pick a mode on each video: copilot or agent. For agent mode, choose to run the agents on your computer or on Fluxcut. Either way, choose one agent or two: a maker alone, and you approve every gate; or a maker plus a reviewer, ideally another model, that approves the gates you allow.

Connect your agent — a key, one command, and the playbook it follows.

COPILOT

You make it

Approve, edit and upload at each step in the app. The default.

AGENT ON YOUR COMPUTER

Your agents make it

Claude Code, Codex or Grok CLI builds the video with Fluxcut keys and the playbook: the brief, the footage, the lines. Free on our side.

AGENT ON FLUXCUT

Fluxcut's agents make it

A Grok maker runs on Fluxcut, its spend capped. It films your public pages itself; for a signed-in screen it asks you to click Record.

How it works

Fluxcut or your local AI agent writes the script, gathers the screen footage, records the voiceover, composes the music, paints a thumbnail and renders the finished video. You (or another agent) review and approve each step before anything is published.

  1. 01

    planned with you

    Say what the video is for.

    From one paragraph, Fluxcut writes the brief: a title, who it is for, the pains it names and the value it argues.

    You: Approve it, edit a line, or send it back with a note.

    With agents: The maker writes and revises the brief; a reviewer agent checks it against your paragraph.

  2. 02

    planned with you

    Create the footage.

    Fluxcut lists the shots it wants: a screen recording here, a screenshot there, each with a reason.

    You: Upload what you have. Skip a beat you cannot show and it drops out of the video instead of blocking it.

    With agents: The maker films what it can reach and asks you for the rest: click Record in the browser for a signed-in screen.

  3. 03

    planned with you

    Timeline and script, kept in step.

    The shots become a timeline with seconds on each one, and a script with a line per shot, counted in words against those seconds. Edit either side and the other follows until both agree.

    You: Reorder shots, set how long one holds, rewrite a line. Approve the script line by line.

    With agents: The maker fits the lines to the seconds; the reviewer approves or sends one line back with a note.

  4. 04

    made by Fluxcut

    Voice, music and a thumbnail.

    Each line is recorded as its own take. A music bed is composed to the exact length and sits under the voice. Thumbnails are drafted from the brief.

    You: Choose the voice, the delivery and the mood. Listen, pick a thumbnail, or ask for another take with a note.

    With agents: The maker chooses and asks for retakes; the reviewer approves the gates you allow it.

  5. 05

    rendered

    The final video, rendered.

    Picture, voice over music, loudness levelled for the platform. No AI in this step: the same inputs give the same file, every time.

    You: Watch it.

    With agents: No agent renders. Unless you allow it, the final video waits for you even with a reviewer.

  6. 06

    rendered

    Publish when you say so.

    Title, description, your thumbnail and the final cut are assembled and held.

    You: Approve, and it goes out. Change anything afterwards and Fluxcut tells you what it must remake and what still stands.

    With agents: Nothing. Publishing is yours alone.

THE PART THAT MAKES IT USABLE

Change one thing, remake only that

Edit anything, at any point. Fluxcut knows what depends on what, so it remakes only the pieces your edit touches. Your approvals on everything else stand. Try an edit:

THE EDIT You rewrite line 3 of the script, to the same length.

BriefFootageTimeline
Script
line 1line 2line 3line 4
Voiceover
take 1take 2take 3take 4
MusicThumbnailFinal video

Take 3 is re-recorded. The other three takes keep your approval. The music follows the timing of the voice, not its words, so it stays. The final video is re-rendered, and publishing waits for you again.

You changedRemadeKeptStill usable

Four promises

APPROVALS STICK

An approval is tied to what you saw

Approve a script and that exact script is approved, not a checkbox on a page. If anything it depends on changes, the approval lapses and the step waits for you again. Nothing is approved by default, and nothing is approved by a timer.

CHECKED FIRST

Every take is measured before you hear it

Does the take fit its shot, is it loud enough, does it clip, does the music leave room for the voice. A take that fails is retried, up to three times, before it reaches your queue. What lands there has passed.

A NOTE IS DIRECTION

Send it back with a sentence

The next take is made for your note, not just made again. And you send back one line, one take or one thumbnail, never the whole voiceover because one word was wrong.

AGENTS HAVE RAILS

No agent marks its own homework

No agent approves its own work. Publishing and escalations are yours. Spend stops at a cap.

ONE PARAGRAPH TO START

Your first demo video, with or for you

Describe the product, or hand it to your agents.
The run starts at once and stops at the first thing that needs a decision.

Connect your agent