Pricing 2 min read The Fulta team
AI Credits and Cloud Credits, explained
Why Fulta meters building and running separately, what each balance pays for, and how we made sure you cannot get a surprise invoice.
Almost every complaint about usage-based pricing comes down to the same thing: the bill arrives after the spending, and nobody can tell which part caused it. We split the problem in two.
Two balances, two jobs
AI Credits are spent while the AI works: planning, writing code, reviewing the result in a browser, and the sandbox compute that build runs on. Building costs AI Credits. Nothing else does.
Cloud Credits are spent while your published apps serve visitors: requests, CPU time, bandwidth, storage and database. A quiet week costs almost nothing; a week on the front page of a newsletter costs more.
Keeping them apart means one cannot eat the other. A successful launch does not leave you unable to fix a typo, and a long building session does not take your app offline.
What a credit is worth
One credit is one cent. That is the whole formula for top-ups: $10 buys 1,000 credits, $25 buys 2,500, $50 buys 5,000. We do not mark top-ups up, because a credit that costs more than it says would defeat the point of naming it.
Plan allowances work the same way: the Free plan includes 200 AI Credits and 100 Cloud Credits a month, and Pro includes 1,500 and 500.
The parts that stop a surprise
- You see the cost of a change right after it finishes, not at the end of the month.
- New work does not start when a balance is empty. Stopping is the default; overspending requires you to turn it on deliberately.
- A warning arrives while there is still headroom, not at zero.
- Published apps get a grace period before they pause, so a busy weekend is recoverable.
- Usage is broken down per app, so you know which project is the expensive one.
Why not just charge a flat monthly fee?
Because building an app and running it have genuinely different costs, and a flat fee has to assume the worst case for both. That makes a small project subsidise a large one, and it hides the one number that is actually useful: what did this change cost?
We would rather show you the number.
Full details on the pricing page.