Gemini
Script breakdown, prompt assist, stills, and Veo motion.
Local-first AI video production studio
1VideoTool turns a concept or a screenplay into acts, scenes and directed shots, keeps your cast and locations consistent across them, generates through your provider keys, and finishes the cut on a real timeline. The production is a folder of readable files on your disk — not a project inside someone else’s account.
Why this exists
Every prompt box is happy to hand you six seconds of footage. None of them remember your character's coat, which take you approved, or how any of it becomes a cut. That gap is the whole product.
In 1VideoToolA single generator gives you clips. This gives you a production: story, entities, shots, takes, decisions, a timeline and a cut, all of which outlive whichever model made the pixels.
In 1VideoToolThe project, the assets, the timeline and the exports are files in a folder you chose. Generation goes straight from your machine to your provider.
In 1VideoToolAds and product promos are outputs of a production system, not the product. Campaign strategy and publishing belong to 1MarketingTool.
In 1VideoToolThe timeline exists to finish a generated production, with the references and decisions behind every frame still attached.
The idea, in three dimensions
A production is a graph — story, entities, shots, references, prompts, takes, decisions, timeline — and it is the durable thing. Models are routes through it. Scroll to watch a scatter of generations become a film.
Bring in a concept or a Fountain screenplay. It is parsed into acts, scenes and shots you can edit — structure exists before a single frame is generated, so the plan can be finished without spending anything.
Every shot carries intent: camera, composition, action, dialogue, duration, start and end frames, motion. The prompt is compiled from that intent, the attached entities and the provider's contract.
Each generation stacks onto its shot as a take, with the prompt and settings that produced it. One becomes active; the alternatives stay reviewable rather than being overwritten.
Approved takes assemble onto a real timeline, still linked to their shots, with dialogue, effects, music, captions, transitions and overlays. Then out: a film and everything that explains it.
The shot below never changes. Only the route to pixels does — with a different capability envelope and a different bill, paid to whoever you chose.
Every surface over one model
Move between them without importing, converting or duplicating anything. Guided Studio shows one decision at a time; everything else opens the whole production at once.
EXT. THE PIER — BEFORE DAWN
Compiled prompt
Close on Mara's hands, salt-cracked, working the rope. High angle, 85mm, slow push in. Practical light only, the pier lamp behind her. Style: bleached coastal noir, 35mm grain.
The rules underneath it
Each one closes off a shortcut that would make the product easier to build and worse to rely on.
01
Models change every few months. Provider and model are adapters attached to a shot, never part of the project schema, so swapping one does not invalidate the film.
02
A prompt is a compiled artifact derived from shot intent, entities, style and the provider contract. You keep directing after the model changes.
03
Results are never silently replaced. One take is active; the rest stay on the shot with the prompt and settings that produced them.
04
Character, product, location, wardrobe, voice, lighting and frame continuity are recorded against the production, not held in your head or in a chat scrollback.
05
A generation plan shows capability and price before it starts, then records what was actually spent. Your keys, your providers, no markup on compute.
06
Approval is recorded against a revision and an artifact. It is not a dialog that disappears when you close it.
The production folder
The production directory is the source of truth: versioned JSON, your media, and append-only ledgers. Open it in an editor, put it under version control, move it to another machine, or walk away entirely — nothing about it needs 1VideoTool to stay readable.
harbor-light/├─ production.1video.json schema, format, fps, revision├─ story/ screenplay.fountain · structure.json├─ entities/│ ├─ characters/ products/ objects/│ ├─ locations/ styles/ voices/│ ├─ brands/├─ shots/ shot.json · references · takes · prompts├─ timeline/├─ assets/│ ├─ source/ generated/ audio/ proxies/├─ deliveries/ every export lands here├─ .1videotool/│ ├─ revisions/ a snapshot per bump│ ├─ jobs/ resumable queue state│ ├─ ledgers/decisions.jsonl│ ├─ ledgers/costs.jsonl│ ├─ ledgers/approvals.jsonl
Finish and deliver
Every export lands in the production's own deliveries/ folder, and a delivery only reports success once the file exists on disk.
MP4 through ffmpeg
Board timing before generation
PDF, shot by shot
Frames as files
FCP7 XML into your NLE
Local transcription
The readable folder itself
What was made, by which model, at what cost
Providers, keys and agents
Generation goes straight from your computer to the provider you configured. No StoicSoft relay, no resold credits, no account in the middle.
Script breakdown, prompt assist, stills, and Veo motion.
Second image and video adapter.
Local animatic and MP4 export when it is on your PATH.
1VideoTool ships an MCP server that exposes production commands rather than UI coordinates: structure, shots, takes, gaps. Every mutation has to name the revision it expects, so nothing silently overwrites an approved take. It detects the CLI agents already installed on your machine — and an agent runs only when you write an explicit @mention.
Who it's built for
“Carry a story and a visual world through dozens of generated shots without losing control or starting over.”
Narrative shorts, trailers, music videos, previs — across several models, because none of them is best at every shot.
“Give my team one inspectable production where every shot, reference, take and decision is connected.”
Treatments, storyboards and animatics a client can sign off on, with the approvals recorded against a revision.
“Turn one approved creative into controlled variants without a reshoot or an untraceable mess.”
Many cuts across products, markets, formats and languages, all traceable back to one master production.
“Make a complete video without first learning professional production software.”
A guided path from script to cut, with the full workspace waiting on the day you outgrow it.
Cost is part of direction
A generation plan prices itself against your actual shot durations before the request leaves your machine — and you pay the provider directly, because StoicSoft takes no cut of generation.
A generation plan shows capability and price before it runs, and says so plainly when a provider does not publish a rate rather than inventing a number.
Decisions, approvals and costs are written to JSONL ledgers inside the production as they happen, so the spend has a history you can read.
Generation goes from your machine straight to the provider you configured. You are billed by them, at their price, with no resold compute and no credit system in between.
Story, shot planning, entities, board, animatic, timeline, captions and every export are deterministic local work. None of it calls a paid model at all.
One-time desktop licence
Not published yet
You buy the application once and it keeps working on the machine you installed it on. The amount is not published because the figures in the product requirements are labelled hypotheses, and publishing an unvalidated price is worse than publishing none.
Ask about the private betaPrivate beta with design partners. Pricing is being validated against real productions first.
Free of compute cost
Most of a film
Remote generation is billed by the provider you chose. Local editing, rendering and export cost nothing at all.
Questions
Yes. Open Harbor Light, the bundled twelve-shot sample, and everything deterministic works with no keys: story, board, takes, timeline, storyboard PDF, captions, FCP7 XML and manifest export. Keys only buy you new generation.
A Gemini key covers script breakdown, prompt assist, stills and Veo motion. A Runway key is the second image and video adapter. You add the keys, you are billed by the provider, and there is no markup in between.
Nothing. Provider and model are adapters attached to a shot, not part of the project schema. The story, entities, shots, references, takes, decisions and timeline are yours and stay readable.
In a directory you choose, as versioned JSON, media and ledgers. That folder is the source of truth — you can read it, back it up, put it in version control, and open it without the app.
Not if you have one you like. The timeline is there to finish a generated production, and FCP7 XML export exists so you can take the cut into your usual NLE with the structure intact.
1MarketingTool owns campaigns, publishing and analytics; it can send a brief here and receive finished assets. 1ShowcaseTool owns screen capture and product demos, and can send recordings in. 1VideoTool owns the editable production itself.
It is in private beta with design partners now. The price is not published because the figures in the product requirements are explicitly hypotheses, and they are being validated against real use first.
Private beta
1VideoTool is open to a small group of design partners — filmmakers, directors and creative teams who are already fighting their generators. Tell us what you’re producing.
No account needed to open a production. The folder is yours either way.