Skip to content
Sign in Start free

About Studio.

Short, and specific

No founding myth, no team photograph, no stock imagery. What follows is what the product is, why it was built, the rules it is held to, the things it will not do, and what does not exist yet.

What it is

Studio takes the footage you already shot and returns a finished video, plus vertical shorts — and it shows you every cut it made.

Raw footage in. A finished video out. And you'll see every cut. You upload one recording of any length, or several files; Studio reads them, hears every word, cuts the retakes and the dead pauses, plans every visual against what you actually said, draws the video, and hands you the reasoning alongside the result. Each cut, card, zoom and pause is written down with the reason it happened — nothing hides behind the word “processing”.

Start free — 30 minutes included See the whole pipeline
The product in its own words

Studio is the name in the code, in the routes, in the page title and in the documentation. The vocabulary on this site is the product's own vocabulary, deliberately: a job is one video being edited, a project is a container of jobs with their own preferences, a version is each new cut produced from your feedback, a short is a vertical clip cut from a long video, and credits are minutes of source footage — never “coins”, never “points”. Screenshots, docs and tickets have to agree, so the interface speaks the words the API speaks.

It was built by someone editing his own videos.

The person who made Studio was cutting his own videos by hand — retakes, pauses, captions, cards — and wanted the machine to do the cutting while still showing its reasoning. That is the whole origin: no realization in a taxi, no all-night session that changed everything, no founding story worth retelling. There is an editor who got tired of the same hour of work, and a decision that the tool would explain itself rather than ask to be trusted.

That is also why the product is shaped the way it is. A tool that hides its decisions has to be believed. A tool that writes them down can be checked — and being checkable is the only reason to trust an edit you did not make.

Principles

Five rules, each already true in the code

Not aspirations. Every one is enforced by something you can run, and the file that enforces it is named underneath.

01 — Evidence over adjectives If we say it, a check proved it. Every claim about the product carries a gate with a CHECK, an EXPECT and recorded EVIDENCE. When a number changes, the page carrying it changes with it. Nothing is stated because it sounds good.
02 — Never speak for the customer No word on screen that nobody said. Before anything is drawn, every number and phrase planned for a card is checked against your transcript. A card with an unspoken word is dropped and that sentence is planned on your face instead. It is enforced by a test, not by good intentions.
03 — Show the seams Decisions, reasons and errors are visible by default. Each cut, card, zoom and pause is recorded with the reason it happened, in the order it happened, and you can read the whole edit before you watch it. Errors are shown in full, with the log tail and a button to continue — not a dead screen and not a spinner.
04 — Honest time, honest money Measured estimates, credits in minutes, free revisions. The time left is fitted from how long this server actually took on footage like yours, and it deliberately rounds late rather than early. A credit is one minute of source footage, charged once when the video finishes. Ask for twenty changes and it costs the same as asking for one.
05 — Calm, not caffeinated “calm, precise and data-first. No stock footage, memes, emoji rain, hype or fake urgency.” The owner's own brand rule, applied here unchanged. It is why this site has no countdown, no testimonials with stock faces, no exclamation marks — and why the limits are printed next to the features rather than buried in a footnote.
Limits

What Studio refuses to do

Four refusals. They are the product's shape, not a list of missing features — a tool that did any of these would be worth less than one that does not.

It will not invent a shot you did not film
If the footage has no shot for the moment that needs one, the visual plan is changed. Nothing is generated and passed off as yours.
It will not write a claim you did not make
It will not phrase a sentence for you, sharpen your point, or add the adjective you left out. The video says what you said.
It will not put a number on screen nobody said
A figure becomes a card only if those words are in your transcript. The word check drops the card otherwise, and the decision log records the drop.
It will not fake a render
You get the real file or the real error, with the full report and a way to continue from the last saved piece. There is no placeholder download and no silent success.

How each refusal is checked: how we prove it · what other tools do instead

Where it is going

Real gaps, taken from the product's own list of what does not exist — not a wish list dressed up as a plan.

Each item is marked next or later. There are no dates here and there will not be: a date promised to a customer is a claim, and this page only makes claims it can check.

The one you can already see the shape of
The credits ledger is written by the backend today — every grant and every charge, with its reason and job id — and nothing shows it to the person it belongs to. That is the gap this redesign closes first.
Not built yet
1 Payments and plan tiers next
2 A credit ledger you can see next
3 Email notifications and password reset next
4 Teams and seats later
5 Integrations — Drive, Dropbox, YouTube, S3 later

Payments: no checkout, no invoice and no card on file — “payment is out of scope for 0.6”. Tiers: the schema has no plan column at all, only credits and a role. Email: none anywhere, which also means no verification, no receipts and no password reset. Teams: one account is one person. Integrations: nothing leaves the server but the file you download.

The version

Studio 0.7.3 — the string in the repository and the one the server reports, read from studio/VERSION and returned by GET /studio/api/me. It is a small number because the product is early, and this page would rather print it than imply otherwise.

Read the changelog What the server is doing now

The quickest way to judge all of this

Is to run one of your own videos through it. The first 30 minutes are free, the word check runs on a free job exactly as it runs on a paid one, and the decisions are readable whether you agree with them or not.

Start free How we prove the claims

Rather talk to a person first? Talk to us, or book twenty minutes.

Keep reading
Every stage of the edit, named The four tiers and their limits How Studio differs from the alternatives Privacy and data handling