Plans, quotas and billing

An authenticated account still needs an active Lordbase subscription for protected operations. Workspace ownership, membership and engine credentials do not replace that prerequisite.

The owner’s plan determines database creation limits, database-user limits, storage/connections assigned at provisioning and schedule retention. Some feature checks, such as pause, also use the acting account. A collaborator can therefore encounter a subscription failure even when the workspace owner has capacity.

Use Billing and the account/plan APIs to inspect status, limits and usage. Do not hardcode the illustrative numbers in API examples as product pricing or guaranteed allowances. Consult the plan currently offered to your account.

When a plan operation fails

• A quota error with LIMIT_EXCEEDED means the requested resource/retention exceeds the allowed amount; inspect the returned limit and current usage.
• ENTITLEMENT_UNAVAILABLE means entitlement verification failed. It is not evidence that buying the same plan again will fix the issue.
• Refreshing cached plan information only refreshes the check; it does not activate or purchase a subscription.
• The reviewed dashboard’s plan-loading/activation flow has an availability gap. If Billing cannot load plans or complete activation, capture the status/message and request ID, then contact Lordbase support. These docs do not provide an alternative purchase API that bypasses that flow.

Read account and plan endpoints and API errors.