Billing, entitlements, and quotas
Turn plan configuration into authoritative server policy.
On this page
Canonical source
This public guide is distilled from docs/BILLING.md and docs/CONVENTIONS.md. Keep implementation detail in those repository documents.
Commercial state is not UI decoration
A typed catalog drives Stripe, Lemon Squeezy, Polar, or Mollie hosted checkout plus the pricing page. Verified provider events project subscriptions and fulfill one-time access or credits, while entitlement keys define the server-owned commercial policy.
Usage survives retries
Concurrency, billing-period, session, and API-key limits use a durable ledger and stable event identity. UI gating can explain a decision, but authenticated services reserve and enforce usage again.
Was this page helpful?
Feedback is stored only in this browser in the starter implementation.