Every pricing model looks simple on the pricing page and turns out to have asterisks. This post is the no-asterisks version of ours, written the way we'd want another product to explain theirs.
The two kinds of credits
| Monthly allowance | Credit packs | |
|---|---|---|
| Comes from | Your plan (including the free one) | Bought separately, when you want |
| Expires? | Resets each billing cycle — doesn't roll over | Never |
| Spent | First | Only after the allowance is gone |
The logic: the allowance is your plan's included usage, and letting it stack forever would just be a strange savings account. Packs are money you paid specifically, so they keep their value indefinitely. The spend order means you never burn a pack while an allowance sits unused.
What consumes credits
Agent work does: builds and rebuilds, research runs, marketing draft generation, optimization passes. Rates differ by action — a full app build is not priced like a copy tweak — and the pricing page lists them by type. What doesn't consume credits: your published sites staying up, browsing your dashboards, reading your analytics, or asking the assistant questions.
The edge cases, honestly
- Run out mid-build? The run pauses and says so — it doesn't fail silently or eat the credits. Top up or wait for the reset, then re-run.
- A run fails from a platform fault? Contact us and we re-credit it. Store rejections or your revoked third-party credentials aren't platform faults — though we'll help fix those too.
- Refunds? Untouched packs within 14 days, and a charged-but-unused new cycle within 14 days. Consumed work is consumed. The full text is the Refund Policy, and it's short on purpose.