Case study

From a topic to a finished film

A 10-stage AI pipeline, and the studio to steer it.

Client
3DLabs
Timeline
4 months · May 2026 – Sep 2026
Scope
AI, Product
Picking a shot for every scene.
Picking a shot for every scene.

Type a topic, say “The History of NASA”. 3DLabs writes the story, plans every scene, renders consistent stills, animates them, adds narration and sound, and exports a finished documentary.

The brief

3DLabs wanted a documentary studio, not a script generator. A creator types a topic and gets back a finished film: researched story, scene plan, footage, narration, sound, and a package ready for their editor.

The bar was a film the creator would put their name on, not a reel of impressive but random AI clips.

The hard part

Every stage feeds the next. A weak still becomes a weak clip, which becomes a mistimed sound cue three stages later. Fully automatic meant one bad decision early could ruin a film nobody could fix.

Renders are also slow and expensive, and the best model for each stage keeps changing.

  • Errors compound across ten stages
  • Long, costly renders that sometimes fail
  • A model landscape that changes every month
The video stage, scene by scene.
The video stage, scene by scene.

What we designed

A studio that moves through the film one stage at a time, Story → Images → Video → Audio → Export, with the creator approving each step before the next one spends money.

Every scene shows four takes side by side, labelled by shot type (establishing, intimate, detail, atmospheric). Pick one, regenerate the rest, and move on. Credits, job history and notifications sit in the sidebar, so the creator always knows what is running and what it costs.

Under the hood

Ten stages, each one feeding the next.

Ten stages, each one feeding the next.

What we built

Behind the studio sits a ten-stage pipeline run by a job orchestrator. Each stage talks to a model-routing layer rather than a specific model, and a registry adds or retires models without touching the pipeline.

Credits are reserved when a job starts, confirmed when it succeeds and released when it fails. Workspaces keep each team's projects, assets and spend apart, and audit logs record what every run used.

  • Job orchestrator with retries and failover
  • Model routing for text, image, video, voice and sound
  • Credit system: reserve, confirm, release
  • Per-workspace isolation, storage and audit logs

Where it landed

3DLabs ships films a creator steers scene by scene, on a stack that can adopt next month's best model without a rewrite.

Built with

  • Next.js
  • FastAPI
  • PostgreSQL
  • Redis
  • S3 / R2
  • Docker
  • Gemini
  • Flux
  • Seedance
  • ElevenLabs
  • FFmpeg

Shipped

  • Studio, from story to export
  • 10-stage generation pipeline
  • Model-routing layer
  • Credits, workspaces and teams

Read more about this build