The internal short-video production workstation for
Reference videos to batch renders
Break down references, write scripts, fix storyboards, plan shoots, manage footage — then let Hypit render batches from editing templates, reviewed before release.
Business features open up from S1; today you can sign in and manage your account.
Roadmap
S0 · DoneEngineering baseline
Locked deps, SQLite migrations, RBAC and Hypit compatibility — accepted 2026-09-26.
S1 · In progressReference library
Import collected peer videos, analyses and metric snapshots; filter by product, purpose and status.
S2Script library
Derive sourced script frameworks from references and generate reviewable shooting scripts.
S3Storyboard library
Reusable shot standards: frame, camera, action, duration, acceptance.
S4 → M1Shoot tasks
Merge shooting needs across scripts, grouped by product, location and camera setup.
S5 → M2Footage library
Upload raw footage, trim segments, deliver downloadable clip files.
S6 → M3Template renders
Hypit renders from editing templates, batch combinations, per-clip checks.
S7Feedback loop
Collect performance data, update scripts and templates, run as a team routine.
What you can make
Editing standards
One template, consistent renders.
Structure, sound, captions, pacing and acceptance rules, each mapped to an executable Hypit template. Hypit renders from the same template; reviewers release against the same checklist.
Ships in S6
Selling-point cuts
Unboxing
Demo
Comparison test
Production line
Customer talk
Product launch
Spec walkthrough
Case story
Packaging details
Trial run
After-sales Q&A
Four libraries
Scripts, storyboards, footage, editing standards. All in one place.
Everything production needs lives in one workstation — not in folders and chat threads.
Reusable frameworks, concrete scripts and versions: who it is for, what problem it solves, how to say it, what evidence it needs.
Structure, sound, caption and pacing rules plus executable Hypit templates.
Shot purpose and shooting standards: frame, camera, action, duration and acceptance.
Raw footage, trimmed clips and images — technically checked and ready to download.
Collected peer videos, past analyses and metric snapshots — where scripts come from.
Merged shooting needs across scripts, grouped by product, location and camera, with gaps flagged.
Reference → script
Give it a reference video. Get a shootable script.
Derive a script framework from the reference, then combine it with product facts into a shooting script, storyboard and shoot sheet. Every step keeps its source and version; missing facts are flagged, never invented.
Ships in S2–S4Processed
Script framework extracted
- Audience: buyers of small beverage / cosmetics filling lines
- Problem: changing bottle types means stopping the line
- Delivery: show the result, then the action, then the specs
- Evidence: real changeover footage, a timer, spec captions
- Structure: hook → pain → action → result → specs → call to action
Batch production
One script. 50 different renders.
Each shot gets several candidate clips — some fixed, some rotating — combined by rule. Every clip is auto-checked, then released by a human reviewer.
Ships in S6
4 takes per shot
7 shots × 4 qualified clips each: 4⁷ = 16,384 theoretical combinations.
At least 3 shots differ
Any two clips in a batch differ in at least 3 shots; 300+ rule-passing combinations found locally.
Per-clip auto checks
Decode, duration, A/V sync and captions checked per clip; a single failure recovers without blocking the batch.
Human release
Template owners maintain templates; reviewers release against the pre-publish checklist.
Traceable
Every video has a source, a standard, a trail.
From reference breakdown to render review, every step records its basis and version: which reference the script came from, which standard the shot follows, which shoot the clip is from, which template rendered it.
Sign inReference → script v2Shot #3 · standard card B-07Render #27 · template T-15s-APipeline
Name the step. The workstation has a place for it.
Ten steps ship by stage; steps not yet delivered have no entry point.
01S1Reference video
02S2Script framework
03S2Shooting script
04S3Storyboard
05S4Shoot task
06S5Raw upload
07S5Trim segments
08S5Footage library
09S6Template render
10S6Review & release
Pinned engines.
One workstation.
A pinned Hypit version renders, FFmpeg handles media, business data lives in local SQLite; model analysis runs only within a set scope and budget. Engine upgrades never touch your scripts, storyboards or templates.
For every role
Built for the people who get videos out.
Content lead
Sets product, audience and claims; reviews scripts; reads the feedback loop.
Director
Breaks down references, writes scripts, lays out storyboards, merges needs into shoot tasks.
Shooter
Shoots to storyboard standards, delivers raw footage to acceptance rules, reshoots with a reason.
Template owner / reviewer
Maintains and verifies Hypit templates; releases renders against the checklist.
Runs on your machine. Data stays home.
Business data lives in local SQLite; raw footage and clips stay in a controlled media directory, never in the code repository.
50 clipsFirst acceptance target: real renders
7 shots × 4 takes, ~2s per shot plus a 1s closing logo — about 15 seconds per clip.
Sign inFAQ
What you may want to know before you start.
Start from a reference.