What do you want to generate?
Every generator is a kit — one JSON file holding a design brief, a preview frame and its canvas sizes. Pick one, or describe a new one and build it by chatting.
Every generator is a kit — one JSON file holding a design brief, a preview frame and its canvas sizes. Pick one, or describe a new one and build it by chatting.
Every product you have designed here, with its full version history. A generation keeps running on the server after you close the tab — reopen the project and you rejoin it mid-build.
Nothing here yet. Pick a kit and describe what you want — the first thing you generate becomes a project, and it names itself after what it made.
Choose a kitDeleted projects are kept here with every version. Restoring one puts it back exactly as it was.
Who is in this business, what they may do, and what it is allowed to spend. Everything here is scoped to this organization alone — another business on this installation can neither see nor change any of it.
This organization's own ceilings. The machine-wide limits apply on top and can only ever refuse, never grant.
There is no self-service sign-up. An owner adds people here. If they have no account yet, give them a starting password — they can change it later.
The person you choose becomes the owner and you become an editor. You keep access to everything you have built; you stop being able to transfer, delete, or read this history. Choose someone who is already a member.
Who changed what, and when. Generations are not here — they are in the usage ledger. Nothing in this log records a password, a token, or a customer's brief.
A published generator is a page your customers use. They never sign in, never see this studio, and never learn it was built here — the page carries your name, your colours and your facts, and nothing of ours.
Choose which of your generators the page should run. Nothing goes live until you press Publish, and you can change everything before and after.
Used verbatim in every document. The generator is told never to invent a name, an address or a phone number, so anything you leave blank is left blank rather than guessed at.
Facts it may state, services it may offer, prices it may quote — one per line. It is told never to go beyond them, and every figure in a finished document is checked against your price list afterwards.
Arithmetic can refuse a figure; it can never approve one. With the prices above, a total the generator works out for itself is reachable — and still a commitment nobody at your business made.
What this tool may read when it runs. It receives only what is ticked here, and of that, only what a request actually matches — never the whole list on every turn.
Nothing yet. Anything you add below as Organization can be shared with several tools.
Nothing attached to this tool yet.
Each code is a customer. A code carries its own allowance and can be revoked without affecting the others.
No codes yet — nobody can open this product until you issue one.
One action offered after the product has been useful. It is a link the customer follows — this platform sends no email and calls no webhook — and the report below counts how many followed it. Leave the label empty for no next action.
Yours alone, on top of the organization's. Either can refuse; neither can grant.
What a customer fills in. Edit any of it — this is what the test submits.
Each round generates one artifact with the kit as it stands, judges it against the kit’s own rules and what you asked for, then rewrites the single field most responsible for the worst problem — and goes again. It stops early when the critic passes it.
The critic reads the generated HTML source, not a picture of the page, so it judges structure, completeness and copy — never how the spacing looks. The score grades that round’s artifact, not the kit, so it moves around with generation luck — read the findings, not the number. Cost scales with the artifact: about $0.10 a round for a screen, $0.20 for a long document.