Nothing is built until you approve the plan
Creator first works out what you actually asked for — the screens, the
requirements, the architecture — and shows you the plan. Until you press
Approve, no infrastructure is created — planning draws only lightly on
your usage allowance. You can request changes as many times as you like.
Every promise is checked, and you see the receipts
The plan is a list of promises. As the agent builds, each promise is verified
against the running app, and the Proof tab shows you exactly what was
proved, what you confirmed yourself, and what couldn’t be checked. No vague
green checkmarks.
Your app is real, isolated, and yours
Each project gets its own isolated backend — database, authentication, file
storage, secrets — not a shared sandbox. And the code is yours: you can push
the full project to your own GitHub repository on every plan.
How a build works
- Describe it. One sentence is enough to start; a detailed brief works too.
- Configure it. Pick a stack, a build approach (quick or design-first), and a fidelity — Production (strictly verified, safe to hand to a client) or Prototype (fast, gates off, for trying ideas).
- Approve the plan. Review what will be built and which capabilities (database, sign-in, storage…) it will use. This is the moment your workspace — and your spend — actually starts.
- Watch it build. The preview pane updates live as the agent works through the plan story by story: Planning → Your turn → Building → Testing → Polishing → Ready.
- Publish. One click promotes your app to a permanent production URL, with a ledger of exactly which promises were verified.
Creator is currently in closed beta. Signing up puts you on the request list;
see the quickstart for how access works.
Where to go next
- Quickstart — from sign-up to your first live app.
- Core concepts — projects, rounds, tiers, fidelity, and what “verified” means.
- Capabilities — the real infrastructure your app can use.