NOMAD Works offline
Once your models are downloaded, nothing needs a connection. No account, no licence check, no telemetry call.
Session & Album
A campaign is not
A campaign is not
a folder of PNGs.
Real projects are chains: generate, upscale, edit, relight, branch, try it the other way, come back to the third version. Sessions capture that whole tree automatically, and the Album is where you find any of it again.
Sessions
Everything you did, kept in order.
A session is a persistent workspace at its own address. Each flow run is recorded with its inputs and its outputs, so the history is not a list of files — it is a record of decisions you can walk back through.
- Auto-captured. No manual saving. Run a flow inside a session and the output lands there.
- Chain any flow, any order. Generate → Upscale → Edit → Relight → Export. Each step feeds the next.
- Duplicate and branch. Copy a whole run to explore a different direction without losing the first.
- Export as Markdown, HTML or zip. A readable record you can hand to a client, or a package you can import on another machine.
- Story projects. Multi-scene narratives keep world context and scene history so continuity survives across a whole series.
Depots — the active collection
A depot is a private collection tied to one idea, grouping backgrounds, characters, assets and flow results. Only one can be active at a time; while it is, every generation files itself in automatically under the flow category — with no selection step and nothing to remember.
From any result card you can also send an image in deliberately, as a character, a background or a plain asset — which is how a good generation becomes a reusable part of your library instead of a file you will never find again.
Album & Explore
Find the one from three weeks ago.
Everything you generate is written to a folder you choose, with its metadata intact, and indexed by a paging service that does not cap the history. Four different views exist because finding an image and organising a hundred of them are different jobs.
- Album — paged gallery with hover cards, per profile and per agent.
- Explore — browse previous generations and collections in depth.
- Organize — a grid-and-cell view for grouping images into sets.
- Flow gallery — a lightbox feed of the results from each individual run.
Build
The space where the library gets made.
Build is where characters, backgrounds and depots are created and maintained — the reference assets that make every other space more useful. Save a subject once and it is available as a reference in any flow, in any space, from then on.
Where all of it lives
On your disk. In a folder you picked.
There is no cloud sync, because there is no cloud. The studio writes PNGs with metadata to the output folder you configure, and the registry that tracks styles, depots, sessions, profiles and template packs is JSON with atomic backup copies.
Atomic writes
Every registry write goes through a shared helper that keeps a .bak copy — so a crash mid-save does not cost you a library.
Vanish mode
A private profile whose generations pass through temporary memory and never reach storage. For the test runs you would rather not keep.
Start a session. Fill it up.
Every flow you run inside it is captured, chained and exportable — including the ones you decide against.