Product
Organization billing plan, Stripe Portal boundary, usage limits, and read-model ownership.
Billing and usage are organization-scoped account surfaces.
CentraKit uses Stripe Billing for subscriptions. The SaaS app keeps a local read model for the Billing & Plan page, while Stripe remains the source of truth for subscription status, invoices, payment methods, and the Customer Portal.
Users with billing permissions can:
Checkout and portal return pages are UX hints. Verified webhooks update local billing state.
Audit logs are included on every plan. The billing plan feature catalog is the presentation source for availability and retention copy:
The daily retention workflow applies these limits in bounded batches. The Enterprise override lives on the organization subscription; it does not create another plan or feature catalog. See Audit Logs for visibility, export, and data-safety details.
Usage and limits are organization-scoped and plan-aware. CentraKit records raw operational events, normalizes them into an append-only usage ledger, aggregates the current billing period, and reports billable overage to Stripe metered usage. Local usage remains the source of truth for the Usage & Limits page and reconciliation.
Initial billable meters:
The selected subscription plan defines included quantities for each billable meter. Usage above the included quantity is billed as metered overage instead of blocking the organization.
Additional non-billable meters are tracked or reserved for future limits:
Workflow AI calls consume the same AI input and output token meters as chat and inbox AI.
See Stripe Billing for environment variables, webhook events, and go-live checks.