Pricing
Metered on what your app uses, capped where you say, and reconstructible line by line.
The price book is not published yet.
Rates are set once, written down in one place, and published as a whole — together with a worked example of a traffic spike at 2× and 10×, and a per-app cost model with a ceiling. Until that exists, this page states the model and prints no numbers. What follows is the part that is already decided.
How the bill is put together
- Metered on
- Requests, CPU-time, egress and storage.What the app actually uses, on dimensions you can forecast.
- Seats
- No per-seat tax.Adding a teammate does not change the meter.
- Caps & alerts
- Hard caps and alerts are features, not fine print.You set the ceiling; it is part of the product, not a support request.
- Overage
- Off by default.A paid plan never charges past its subscription price without you turning it on.
- Model tokens
- BYOS — your own model subscription does the building.No marked-up tokens on your bill.
- The bill itself
- Reconstructible.You can see what you used, and why.
What gets published here, and when
- The price book — every rate, on one page.
- A worked spike example: the same app's bill at 2× and 10× its usual traffic.
- A per-app cost model with a ceiling, so a studio can price a client project before building it.
Each of those is an artifact, not a date. They appear here when they exist.
Frequently asked questions
What am I charged for?
Serving and operations: the requests your app answers, the CPU-time it spends answering them, what it sends out, and what it stores. Not the number of people on your team.
What do the rates look like?
They are not published yet, and this page will not guess at them. The price book is one document with every rate on it; when it is published it lands here, in full.
Can a bad week produce a bill I did not expect?
You set a hard cap. Overage is off unless you turn it on, so a paid plan stops at its subscription price rather than running past it, and the alerts that lead up to the cap are part of the product.
Do you charge for the model that builds the app?
No. You bring your own model subscription, and it bills you directly. We never resell those tokens, so there is no credit meter on this product.
Can I see how a bill was arrived at?
Yes — that is what reconstructible means here. Every line traces to metered usage you can inspect.
What if I want to leave?
Your app is plain Nim, the framework is Apache-2.0, and the steps for leaving are written down in a published exit runbook.