Start free. Scale when you ship.

Most tools in this category quietly hand you a second problem: the subscription covers the editor, and then you go and open accounts with a database host, an auth vendor, an email provider and a hosting platform, each with its own dashboard, its own keys and its own invoice. code-anything is priced the other way round. The platform writes the integration code for those services from vetted bricks and runs the sandbox, the builds and the hosting itself, so a plan buys you the whole path from a sentence to a running, hosted application. The accounts those services run on are a separate, explicit step, and for Stripe and Resend they are your own.

Within a plan, the variable is work. An agent run costs real money to execute — model calls to read your codebase and write the change, and sandbox compute to install dependencies, run your tests and produce a build. Credits are simply how that cost is expressed in your account, so a month where you shipped one small copy change does not cost the same as a month where you built three features.

Where the allotment comes from

Each paid plan grants a fixed number of credits at the start of every billing period: 16,000 build credits and 1,000 runtime credits on Starter, 80,000 and 5,000 on Pro, and 400,000 and 25,000 on Team. Free accounts are provisioned with 50 build credits and 500 runtime credits when you sign up, and topped up to that allotment on the first of each month. Paid allotments reset rather than accumulating — a quiet month does not bank credits for a busy one.

Why a build costs what it costs

The size of the change is the main driver. Renaming a button touches one file and needs one verification pass. Adding a feature that stores data means the agent has to understand your existing schema, write a migration, add an API route, build the UI, and then run typecheck, tests and a real build before showing it to you — see code intelligence and sandbox verification for what that involves. Bigger, more ambitious work uses more credits because it genuinely takes more work.

What bounds a single run

Your credit balance is the ceiling. A build is allowed to spend what you can actually afford and no more, rather than being cut short by an arbitrary step or token limit that has nothing to do with your account. Two other bounds sit around that: your plan decides how many builds may run at once — one on Free, three on Starter, six on Pro, twelve on Team — and every account, on every plan, sits behind a $25-a-day spend ceiling that resets at 00:00 UTC, so a runaway loop can never empty a balance overnight. Your current plan, allotment, remaining balance, parallel-build limit and renewal date are all shown on the Billing page inside the product.

Credits are checked before a run starts and deducted after it finishes, from the cost that run actually incurred. That ordering is the whole answer. A build you have already received is never rolled back, reverted or withheld because of billing — the work is yours, the preview stays up, the code stays in your workspace. What stops is the next run.

Before a build starts

If the balance is empty, the run does not begin, and you are told plainly: out of build credits, top up or upgrade to keep building. If the credits run out partway through a build, the run stops there — but nothing it had already written is discarded. Top up and start it again and it carries on from the files it had reached, rather than from nothing.

Your three options

• Wait for the refresh. Every plan, Free included, gets a fresh allotment at the start of the next period — reset on paid plans, topped up on the first of the month on Free. Near the end of a cycle this often costs nothing.
• Buy a one-time top-up. Credit top-ups are purchased through Stripe Checkout from the Billing page and add to your balance instead of resetting it, so they stack on whatever your plan has already granted. Larger top-ups deliver more credits per dollar. A top-up is not a subscription — it does not change your plan and there is nothing to cancel afterwards.
• Move up a plan. If you are running out every month, the allotment is the wrong size rather than the usage being wrong. A higher plan grants more credits and lets more builds run in parallel.

Runtime credits behave the same way from the other side of the launch: they meter events your shipped app produces, so an app that sends few emails and fires few automations barely touches the bucket, and the ones that do are visible in the same place. Unlike build credits, a runtime deduction is refused rather than applied when the bucket is empty, so a live app cannot quietly run up a debt.

The hidden cost in the left-hand column is rarely the subscription. It is the afternoon spent verifying a sending domain, the evening spent debugging a webhook signature, the week where auth almost works. That work does not disappear because you used an AI editor to write the frontend — it just moves to the point where you try to ship. Having it already written, vetted once rather than rediscovered per project, is the part of the price that is easy to underestimate on the way in and obvious on the way out.

The honest caveat about provider costs

Pre-wiring is not the same as paying every bill forever, and we would rather say so here than surprise you later. As an app grows past the free tiers underneath it, the providers — Supabase, Cloudflare, Stripe and so on — bill you directly for their own subscriptions and fees. Those charges are separate from your build and runtime credits, and the Usage page for each project shows an estimated monthly running cost per provider so the number is in front of you before it turns up on a card. What your plan buys is the code, the wiring and the maintenance of that stack, not an exemption from the providers underneath it.

If you are weighing this against a specific tool, the comparison pages lay out where code-anything differs from each one, and the platform overview explains how the build, verify and deploy pipeline fits together.

How you pay

Paid plans are billed monthly through Stripe Checkout. You never hand card details to code-anything directly — checkout happens on Stripe, and your subscription renews automatically at the start of each billing period. When the renewal payment succeeds, that period’s credit allotment is granted to your account.

Starting without a card

The Free plan requires no payment method at all. You can sign in, describe an app, watch it build in a live preview and iterate on it before any billing relationship exists. Upgrading is a deliberate act, not a trial that quietly converts.

Changing or cancelling

You can start a checkout for a different plan from the Billing page in your account at any time. You can also cancel at any time; when the subscription ends your account returns to the Free plan and its allotment, and the per-plan limits follow accordingly. One-time credit top-ups are separate purchases — they are not a subscription, so there is nothing to cancel. Fees already paid are non-refundable except where the law requires otherwise; the terms set that out in full.

Teams and organisations

Shared workspaces and roles are planned rather than available — today a workspace belongs to a single account, and collaboration happens around what you deploy rather than inside the workspace. If you need single sign-on, an audit trail, priority monitoring or a dedicated support channel, those are available for larger teams on request — the Enterprise page covers what exists today and what is available on request, without the usual hand-waving.