Guides
Billing
Learn the billing concepts that shape plans, subscriptions, entitlements, and workspace growth.
Billing in Qwibik One is workspace-scoped. A subscription determines which modules, limits, and commercial terms are available to the workspace.
Billing objects
| Object | Scope | Notes |
|---|---|---|
| Plan | Product catalog | Defines packaged capabilities and pricing model |
| Subscription | Workspace | Tracks active plan, lifecycle, and renewal state |
| Entitlement | Workspace or module | Controls access to specific capabilities |
| Invoice | Billing account | Represents charges, credits, and payment status |
| Payment method | Billing account | Used for renewals and balance collection |
Entitlements
Entitlements should be checked server-side before enabling paid capabilities. UI checks are useful for guidance, but they are not an authorization boundary.
const canUseAutomation = await entitlements.has({
workspaceId,
feature: "workflow.automation",
});
if (!canUseAutomation) {
throw new Error("Automation is not enabled for this workspace.");
}Operational guidance
Use a clear billing owner and escalation path for every workspace. For larger customers, document who can approve plan changes, payment method updates, and invoice disputes.
Future API surface
Billing docs should eventually connect to generated API reference pages for subscriptions, invoices, usage records, and webhooks.