com.ikenga.studio · in the shell · Apache-2.0 · coming to the registry
the film lives here.
Studio is the orchestration spine for AI film — script to breakdown to cast, storyboard, generation, and final cut, on one board. It doesn't replace the generators you use. It conducts them.
Studio runs in the Ikenga shell today and a real master MP4 has shipped end-to-end from it. It isn't published to the registry yet, so there's no install command here — it'll appear in the catalog the moment it ships. The in-app screens below are the locked interface concepts, shown on the 'The Forge' demo film.
The tools make shots. Nobody makes the film.
Every AI generator is an island. Between them, the actual film — the through-line, the consistency, the record of what made each frame — falls on the floor.
- Your cast & world drift. No shared identity between the still you generated and the shot you animated. The face changes.
- Prompts rot in spreadsheets. Past a few dozen shots, every prompt lives in a sheet nobody can keep in sync.
- No record of the take. Which model, which seed, which settings made this clip? Re-editing means guessing.
- Re-stitching by hand. Change the script or a character and the whole downstream chain is a manual re-run.
Ikenga is the spine — not another generator
Studio is one place for the script, the cast, the locations, the prompts, the clips, and the cut. It holds identity and provenance so nothing drifts and nothing is lost. It doesn't replace Higgsfield, Flow, or fal — it conducts them.
Higgsfield, Flow, and fal make shots. Ikenga makes the film.
Script to cut, one continuous board
One board carries the work from the first line of the script to the delivery master:
Script → Breakdown → Refs & Cast → Storyboard → Generate → Stitch & Edit Studio owns the authoritative render and approval state for every shot; a groundwork film plan mirrors it for production management.
Six surfaces, one project
These are the locked interface concepts, shown on the wordless demo short “The Forge” — Adaora forging an iron mask through the night.
Two tracks, one board
Automate what should be automatic; keep your hands on what's directorial. Both land on the same shot with the same provenance.
Track A — Studio generates
Studio calls the generator directly through fal.ai — seed-locked, cost-tracked, the result lands on the shot. Best for stills, character & location plates, and fast previews. FLUX · Kling · Veo · Wan · Hailuo · LTX.
Track B — you direct
Web-app tools with no public API. Studio hands you a shaped per-shot prompt package; you generate and drop the clip back onto the shot. Best for directorial craft. Higgsfield · Google Flow · Sora · Midjourney.
Where it stands
Shipping today. Script → board → render → export runs end to end — a real master MP4 has shipped from it. Storyboard canvas, shot & camera metadata, 16:9 / 9:16 / 1:1 framing, FFmpeg stitch with music beds, seven video archetypes, and a ~40-tool MCP surface (the board is fully agent-drivable).
Building — staged. The fal adapter and prompt handoff (the generation spine); breakdown, character / location lock, and the shot ledger; AI-film archetypes and the groundwork film profile for production planning.
Plan it in Groundwork. Shoot it in Studio.
The groundwork film profile owns pre-production — logline, treatment, cast bible, lookbook, shotlist, budget — then hands off to Studio, which owns execution. The idea-to-cut guide walks the whole loop.
film plan produces — palette, scene-mood frames,
the anchor set, and title treatment — locked before a single shot generates.