Skip to main content

Who owns the code?

You do. Every project can be pushed to a GitHub repository you own — on every plan, at any time, including mid-build. The export is the real project source (a standard Next.js codebase, not a proprietary format). See Export to GitHub.

What stacks can it build?

When you create a project you choose between Frontend (Next.js + Tailwind — the default), Full-stack (Next.js with Postgres and authentication), and Supabase (Next.js backed by Supabase). The agent picks the concrete architecture within your choice during planning, and you see it before anything is built.

How do I get access?

Creator is in closed beta. Sign up with email or Google; if you’re not on the invite list yet you’ll get a short request form — tell us what you want to build. Approved accounts sign straight in.

Where does my app run? Where is my data?

Each project runs in its own isolated environment on AWS in the ap-south-1 (Mumbai) region — its own database credentials, its own storage scope, its own secrets, its own network rules. One project can’t reach another’s data. Databases, file storage, and disks are encrypted at rest, and traffic is encrypted in transit.

Is my preview public?

Your preview URL is for development — treat it as private but not secret. Publishing is the deliberate step that creates the production URL you share with users. Preview and production are separate; the preview sleeping never affects your published app.

What can’t Creator do yet?

Honestly, today:
  • Custom domains — published apps live on their Creator-provided URL; bring-your-own-domain isn’t available yet.
  • Self-serve billing — plans and checkout are coming; during the beta, contact us to change your allowance.
  • In-app account security controls — password change and two-factor authentication aren’t manageable in the product yet (Google sign-in is available at account level).
When one of these ships you’ll see it in the changelog.

What does “verified” actually mean?

That the specific promises the plan made were checked against the running app, with receipts you can read — not that a test suite somewhere went green. The verification section explains how to read them, including what couldn’t be checked means.

How much does a build cost?

Usage is metered in tokens and cost against your plan’s daily and monthly allowances, with live meters on the Usage page and a per-project Cost tab. Planning is deliberately cheap: your workspace — and real spend — only starts when you approve the plan.