The problem
The solution
What QuotaStack does
Every user action lands as a ledger entry — grant, use, reserve, commit, refund. Immutable, queryable, and accurate to the cent.
Demonstration loop. Real QuotaStack ledgers are immutable and queryable via the Audit Log API.
How it works
Set up plans, check entitlements, record usage. That's it.
POST /v1/subscriptions
{
"end_user_id": "user_123",
"plan_variant_id": "var_..."
} GET /v1/entitlements/check
?end_user_id=user_123
&feature_key=api_calls
{ "allowed": true, "balance": 49000 } POST /v1/usage
{
"end_user_id": "user_123",
"feature_key": "api_calls",
"units": 1
} Features
Built for AI, API, and SaaS products. Nothing you don't need.
"Can this user do this?" answered in sub-millisecond latency. Safe to gate every request. Always reflects the latest balance.
Immutable transaction history. Block-based burn-down with priority, expiry, and accumulation caps. Every credit accounted for.
Reserve credits before long-running tasks like AI inference. Commit actual cost after. Unused credits released automatically.
Create, upgrade, downgrade, pause, resume, cancel, renew. Full state machine with automatic free-plan fallback.
Full tenant isolation. Sandbox and live environments on the same account, picked by API key. Scoped keys per tenant.
Every mutation accepts an idempotency key. Safe retries, no double-charging. Webhook delivery with exponential backoff retry.
Compare
Against DIY, usage-billing platforms, SMB subscription tools, and merchant-of-record providers.
Scroll horizontally on small screens →
| Feature | QuotaStack Credit-native | Build It Roll your own | Stripe Billing | Orb Metronome | Lago OSS | Paddle MoR | Chargebee Subs |
|---|---|---|---|---|---|---|---|
| Time to integrate | 1 day | 2-4 wks | 1-2 wks | 1 wk | 1-2 wks | 1 wk | 1-2 wks |
| Credit-native ledger | ✓ | Build | ✕ | ✓ | ✕ | ✕ | ✕ |
| Real-time entitlements | ✓ | Build | ✕ | ✕ | ✕ | ✕ | ✕ |
| Reservations (hold credits) | ✓ | Build | ✕ | ✕ | ✕ | ✕ | ✕ |
| Sub-daily resetting quotas | ✓ | Build | ✕ | ✕ | ✕ | ✕ | ✕ |
| Agent-native docs (.md + llms.txt) | ✓ | — | ✕ | ✕ | ✕ | ✕ | ✕ |
| Merchant of record (tax / compliance) | ✕ | ✕ | ✕ | ✕ | ✕ | ✓ | ✕ |
| Self-host option | ✕ | — | ✕ | ✕ | ✓ | ✕ | ✕ |
| Payment processing | BYO | BYO | ✓ | BYO | BYO | Bundled | BYO |
| Open API / no lock-in | ✓ | ✓ | ✕ | ✕ | ✓ | ✕ | ✕ |
| Pricing | Simple | Eng time | 0.7% rev | Enterprise | OSS / Cloud | % MoR fee | SMB tiers |
You're building AI, API, or credit-based SaaS and need a real ledger, reservations, and sub-ms entitlement checks — with zero payment lock-in.
You need to self-host usage billing for data-residency or compliance reasons and have engineering capacity to run it.
You want a merchant of record to handle global sales tax, VAT, and chargebacks — and you're fine with a flat percentage take.
Your product is classic seat-based SaaS with coupons, dunning, and revenue ops — and you don't need a credit ledger or reservations.
Use cases
Six common billing patterns, each with a complete integration guide.
Tiered monthly plans with credit grants, rollover, and topup packs for burst usage. The classic B2B shape.
Read the guideChatGPT Plus / Claude Pro shape: flat price, generous quota that resets every few hours. No hoarding.
Read the guideA persistent prepaid wallet, time-limited plan packs, and per-message metering with auto-buy on plan expiry.
Read the guideBuy weekly or monthly packs. Reserve credits before generation, commit on success, release on failure.
Read the guideSelling work, not seats. Outcome-priced retainers, long-held reservations for multi-step agent runs, "no outcome, no charge" on failure.
Read the guidePostpaid metered billing with tiered pricing. Period-end usage summaries fire as webhooks for invoicing.
Read the guideThe cookbook has smaller, composable recipes — wallet+plans, pack stacking, free-tier credits, auto-buy from wallet — to mix into your own pattern.
Browse the cookbookFAQ
Tell us about your use case. We'll set up your tenant
with sandbox + live keys within 24 hours.