The Darkroom
Everything developing at once — concurrent runs that survive a refresh, can be stopped and duplicated, with progress pushed to you rather than polled.
The Darkroom is where everything in progress lives. Developing is not one lane you sit and watch. Start a lookbook, start another, duplicate one mid-flight, stop one, send it again.
The Darkroom →What a run is
A run is the set of frames you submitted together: a lookbook's variations, a packshot batch, a single pass. Each frame carries its own state, so a run is rarely just done or not done. It is a count, and the count moves.
| Frame state | What it means |
|---|---|
| Queued | Accepted, waiting for capacity |
| Developing | Being made now |
| Developed | Finished, and its tokens have settled |
| Interrupted | It failed. The hold is released, so it costs you nothing |
| Stopped | You stopped it before it started |
A run of four frames where three developed and one was interrupted reads as exactly that. You are charged for the three.
Progress is pushed, not polled
An idle Darkroom makes no requests and still updates the moment a frame lands. Leave the tab open all afternoon and it costs nothing. A run you started on a laptop is already current when you open it on a phone.
The stream is addressed to your organization rather than to you, so a run one seat started is watchable from another. Your own system can attach to the same stream, which is the first thing worth knowing in the API.
Runs are refresh-safe. Close the tab, come back tomorrow, the state is where you left it.
Stopping and duplicating
Stopping catches the frames that have not started yet. Anything already developing finishes, because a half-made frame is worth less than the tokens already spent on it.
Duplicating is the more useful button. Run a finished set again against a different ground or a different model without rebuilding the setup, and the two sit side by side so you compare them properly instead of from memory. What running it again will cost is shown before you confirm.
Being told when it is done
The house emails you when a lookbook finishes, and the subject says "3 of 4 frames developed" when only some of them landed. That is the intended way to work: start it, leave, come back to a finished set. A packshot batch or a workflow run does not email yet, so watch those here.
To have your own system told instead of you, hold the socket open. Outbound webhooks are designed and not built, which the API says plainly rather than leaving you to discover it.
The cinema
Press Develop and the line becomes the run — every frame on screen before one develops, skips named in your words, and a stop that states its cost.
The library
Everything the house has developed, in two views — a wall for looking and a list for working at a thousand pieces — with a selection bar that names what the house already knows and quotes batch work once, before anything runs.