You bring the what.
Fluvie brings the when.
Not a recorder. A renderer. A screen recorder captures whatever happened to be on screen. Fluvie computes every frame from your description, so frame 412 is the same today, tomorrow, and on your teammate's laptop.
Triggers, not timecodes.
Say "after the title lands, float the subtitle." Fluvie schedules it. Move the title earlier and everything downstream follows. You never type a frame number. Try it: drag the title's start and watch which side keeps up.
On the Fluvie side, the subtitle is anchored after the title, so it followed automatically.
From flutter create to a real MP4.
Five steps, copy as you go. Each command ticks off when you grab it.
Prereqs: Flutter 3.44+ and FFmpeg on your PATH
Preview needs no FFmpeg. Rendering does.
$ flutter --version $ ffmpeg -version
- Make a Flutter appAny fresh project works.
- Add FluvieDrop it into your dependencies and pull it down.
- Install the rendererThe headless CLI that writes the file.
- Write the videoOne scene, a gradient, a title that fades in and pops. Hide Flutter’s own Animation so Fluvie’s wins.
- Preview, then renderRun the app and scrub it live. When it looks right, render the MP4.
Twelve little films, each in one readable file.
Every clip below is a real Fluvie render: text and motion, scenes and transitions, charts that draw themselves, self-typing code, a beat-synced visualizer, captions, the lot. Click any tile to scrub it live.
A small crew. One does the magic.
Eight MIT packages, all on pub.dev. Most people only ever need fluvie. The rest are there when you scale.
- fluvieSTART HEREthe cameraDescribe a video, render an MP4. This is the one that does the magic.
- fluvie_clithe projectionistfluvie render <key> --out file.mp4. Headless, scriptable, no editor in sight.
- fluvie_lintscontinuity supervisorCatches timing, determinism, and layering mistakes before they catch you.
- fluvie_aithe screenwriterTurn a plain sentence into a VideoSpec. Claude, Gemini, Mistral, or Ollama.
- fluvie_apithe render serverAn HTTP server plus a web-safe client. Render from anywhere, host it yourself.
- fluvie_mcpthe assistant's handsAn MCP server so your AI can write and render videos for you, end to end.
- fluvie_mobile_encoderthe on-device camera operatorRender to MP4 on the phone itself, no FFmpeg and nothing leaves the device.
- fluvie_web_encoderthe in-browser camera operatorRender to MP4 in the browser with ffmpeg.wasm, opt-in, nothing leaves the page.
MIT. Inspect it, fork it, host it, keep it.
No black box and no per-render bill. The renderer is open and the frames are deterministic, so the output is auditable: anyone can re-run your render and get the exact same frames. It is free, and it stays free.
- InspectableThe timing resolver is a few hundred readable lines. Read it before you trust it.
- AuditableA frame hash is a receipt. Render twice, diff, trust.
- No lock-inPlain Dart and FFmpeg. Eject any time. Your videos are just code.
- Self-hostableRun the render API in your own Docker. Your media never leaves your network.
- Free, in the openMIT, with a public roadmap and issues. The lints and lessons came from real use.
Same Video, four front doors.
Scrub it live in the browser. Render it from the CLI. Stand up your own render server. Or let an assistant shoot it for you. The engine is the same. Only the trigger changes.
Or just say what you want.
fluvie_ai turns a plain sentence into a real VideoSpec. fluvie_mcp lets your assistant write and render it without you opening an editor. This is the optional easy mode, not the only mode.
Roll camera.
New here? Watch twelve examples render live. Building something? Five steps to your first MP4. Already shipping? Straight to the docs.
You write widgets. Fluvie shoots the film.