Learn

Guest sessions and accounts

A guest session lets you open the studio without signing up. It is a signed cookie, and everything it creates is stored in your browser only — clearing site data removes it, and it is not readable from another device.

Guest runs always return bundled sample media, badged as samples. That is not a trial limitation dressed up as a feature: a run against a real model costs money, and a cookie anyone can mint by clicking a button is not an identity that can be billed or rate-limited.

An account keeps the same canvas, adds cloud projects, publishing, sharing, and — where the deployment has a provider configured — real generation.

The canvas

A project is a connected graph rather than a folder of one-off generations. Each node holds a prompt, its settings, its result and its run history.

Drag from the dot on a node to the dot on another to connect them. The output of the upstream node becomes an input to the downstream one, which is how a character reference reaches the shot that uses it.

Running a selection runs it in dependency order: anything feeding another node finishes first, so inputs are resolved before they are needed.

Run

Runs the selection, or the whole graph when nothing is selected.

Undo / redo

Covers structural edits — adding, connecting, moving and deleting.

Autosave

Writes to browser storage shortly after each change.

Choosing a model

The model field offers two kinds of choice. An intent — auto, best quality, fast, draft — keeps the graph portable: it resolves to whichever model this deployment has mapped to that tier, so a project still runs after the model behind it is replaced.

Pinning a specific model does the opposite: every run uses exactly that model, which is what you want once a look is settled.

The controls below the model field change with the model. A distilled model has no guidance parameter, so no guidance slider appears; a video model that only honours fixed durations shows those lengths as options rather than a slider that would round your choice silently.

Director stage

The director stage is a 3D blocking tool. Place blocks and figures, move the camera, and capture the angle you want to shoot.

A capture is a real render of geometry you arranged, so it is not badged as a sample even when no generation provider is connected — nothing was generated, it was drawn.

Run limits

Live generation is capped per account: a number of runs at once, a number per minute, and a number per day. The meter in the studio bar shows what is left before you reach it.

These exist to stop a loop in a client or one shared login from emptying a provider balance. A deployment sets its own values.

Publishing and Explore

A result you generated can be published to Explore with its prompt, so someone else can build on it rather than only look at it.

Sample media cannot be published: it ships with the app and belongs to nobody, so a card claiming it as work would misrepresent both the result and its author.

Like and use counts on Explore come from real rows — one like per person per work, one row per use. A new deployment starts empty, and it stays empty until people act.