Pricing

Start free. Pay for what you build.

Plans include a monthly allocation of build credits. Prices shown are indicative and configurable per deployment — and the estimated cost of every build is always shown before it starts, so there are never surprise charges.

Starter

Free

30 build credits · 2 projects

  • 2 projects
  • Guided deployment
  • Basic templates
  • Community support
Get started

Builder
Popular

$29/mo est.

200 build credits · 10 projects

  • 10 projects
  • Automated builds
  • GitHub integration
  • Render integration
  • Preview deployments
Get started

Pro

$79/mo est.

600 build credits · 30 projects

  • 30 projects
  • More build credits
  • Advanced integrations
  • Team collaboration
  • Product improvement analysis
  • Priority builds
Get started

Agency

$199/mo est.

2000 build credits · Unlimited projects

  • Multiple client workspaces
  • White-label reports
  • Higher usage limits
  • Team management
Get started

Prices are indicative defaults and may be configured differently on your deployment. Final pricing is always displayed at checkout, and every build shows its estimated credit cost before you approve it.

Build credits

How credits work

Credits are the single unit of usage. A build consumes credits based on what it actually does — and you see the estimate before anything runs.

AI tokens

Blueprint generation, code writing, quality review, and repair-loop fixes all consume model tokens. Bigger, more complex products use more tokens and therefore more credits.

Build compute

Each build runs in an isolated sandbox: installing dependencies, compiling the production build, and executing the full testing pipeline. That sandbox time is part of the credit cost.

Estimated up front

Every blueprint includes an estimated credit cost, and nothing is charged until you approve. If a build fails due to a platform fault, its credits are returned.

Bring your own keys

You can connect your own OpenAI or Anthropic API keys. AI usage is then billed directly by those providers to you, which reduces the credit cost of builds on this platform. Your keys are encrypted at rest with AES-256-GCM and masked after saving.

Billing FAQ

Questions about billing

How do billing and credits work?+

Credits pay for the work the platform performs: AI token usage (the models that write your blueprint and code) and build compute. Every build and change request shows an estimated credit cost before you approve it — nothing is charged until you confirm, and your usage history shows what was actually consumed. Credits do not cover the third-party services you connect: Render hosting, Supabase, and domain registration have their own free tiers and paid prices, billed directly to you by those providers with no markup from us. Your blueprint flags in advance whether the plan requires paid third-party resources, because deployment is not always free and we will not tell you it is.

Can I use my own API keys?+

Yes — bring your own keys (BYOK) is fully supported. You can add your own OpenAI key (starts with sk-, created at platform.openai.com) and Anthropic key (starts with sk-ant-, from console.anthropic.com), plus your own Render, Supabase, and Resend credentials. With your own AI keys, your product's runtime AI features are billed by the provider directly to you at their prices, with full visibility in the provider's dashboard, and you can set your own spending limits there. Every key you store is encrypted at rest, shown only in masked form after saving, and never sent to your browser — decryption happens server-side at the moment of use.

Your first project is on us.

The Starter plan is free and includes enough credits to take a real idea live.