Sora Studio
A Sora workshop with remixing, prompt history and the cost before you render.
The question I was chasing
What does a real production tool around a single video model actually need, beyond the prompt box everyone ships?
The demo version of a Sora app is a text field and a render button. Working seriously with the model is a different job. It means generating a lot, keeping what is close and iterating on it, and knowing what a render costs before committing to it. The model itself arrives with nothing wrapped around it. I wanted to build the part that is missing: the workshop.
The constraints
Everything had to run through Sora's official interface, across Sora 2 and Sora 2 Pro and the resolutions and durations they support. That meant exposing real control without turning the surface into a settings dump.
Iteration had to be cheap and legible. Nudging a result had to beat starting from zero. And the cost has to be visible before the render starts, because frontier video is not free to experiment with blindly.
The decisions that mattered
I built the tool around remixing a near-miss rather than writing a fresh prompt from scratch. Real work is iteration, and nudging something close is cheaper and clearer than starting empty.
Two prompting modes, basic and advanced. That is two surfaces to keep coherent instead of one, and I took the cost because a quick idea and a precise one are not the same job.
I shipped the power-user tooling most apps skip. A pricing calculator so cost is visible before the render. A request viewer so you can see exactly what was sent. And notes plus prompt history, so a session is something you can come back to.
Where it landed
It runs against Sora 2 and Sora 2 Pro, and everything a session needs sits in one place.
I knew the limit going in: this is tooling wrapped tightly around one company's video model. That is what makes it useful now, and what gives it a shelf life. When the model moves, this moves with it or it stops being the workshop.
Part of the Rolling Waves work archive.