Video-Ani turns a one-line premise into a finished, narrated, cinematic episode — script, shot plan, footage, dialogue, assembly, thumbnail and a Private YouTube upload — while an identity engine guarantees the cast never drifts. Approve a character once; the system reproduces exactly that face, outfit and voice in every future scene, or the shot never ships.
The operator dashboard is authentication-gated — it drives real generation spend. This page is the read-only public window into the platform.
Aggregates read directly from the production system.
Counters refresh every minute.
One premise in, one uploaded episode out. Every stage persists its state, so a paused or failed run resumes exactly where it stopped.
Claude writes the script, breaks it into scenes and shots, routes each shot to the right engine and prices the whole plan before a cent is spent.
Veo renders principal cinematic shots, Runway supplies b-roll and transitions, Hedra performs lip-synced dialogue — every call carries the character's full reference package.
Every shot is face-verified against the locked reference sheet and scored by a vision judge on clothing, hair, body and palette. Three strikes and the shot goes to human review — it never enters the edit.
Shots are normalized and cut together, narration is mixed in, a validated thumbnail and SEO metadata are generated, and the episode uploads to YouTube as Private for final human sign-off.
Character drift is treated as a build failure, not an aesthetic quibble.
From a short text brief the system generates design candidates, then a 20-image reference package — angles, expressions, full-body views, outfits, hair and facial-feature close-ups — each image validated against the approved seed before you ever see it.
You approve a design and a reference sheet; the identity locks. Locked versions are immutable — redesigns mint a new version while released episodes stay pinned to the version they were made with, forever.
Face-embedding similarity gates plus a structured vision rubric run on every generated shot. Failures regenerate up to three times, then park in a human review queue where you can approve, retry, or edit the shot spec.
Each episode carries a hard spend cap. The plan is priced up front, every paid call checks the running ledger, and production pauses for explicit approval before a single dollar of overage.
A self-contained service on a k3s cluster — one pod runs the API, worker and state machine; a second, isolated pod holds the browser-driven YouTube uploader.