Skip to main content
Cloud organizations have two plans: Free and Team. A plan belongs to the organization, not an individual account, and pricing is not per seat. Both plans have the same per-project resource limits: 50 data sources, 5 roles, 10 policies, and 10 API keys. Neither plan adds rate limits or feature gates. Owners, Admins, and Billing Admins can view the current plan, Team expiration date, member, project, and Workbook capacity, monthly credits, and add-on credits under Settings → Organization. Owners and Billing Admins can also redeem, upgrade, or renew there, and can buy add-on credits while on Team. Admins have read-only access. Preserved add-on credits are shown as frozen on Free.

​
How credits are consumed

Each organization has two credit pools:
  1. Monthly plan credits are consumed first and do not roll over.
  2. Purchased add-on credits are consumed after the monthly pool.
Only actions that actually consume credits are blocked when the balance is empty. Reading, member governance, usage reporting, renewal, and purchases remain available. Team can purchase add-ons at ¥1 per 10 credits, with a minimum of 100 credits. Downgrading to Free preserves the add-on balance but freezes it; upgrading to Team makes it usable again.

​
Upgrade, renew, and expire

  • Upgrading Free to Team starts a new monthly cycle and grants 10000 credits immediately; remaining Free-cycle credits expire.
  • Renewing an active Team plan only extends the expiration date. It does not reset the current monthly credits.
  • When Team expires, the organization returns to Free, starts a new Free cycle, and receives 10 credits.

​
Exceeding Free limits after downgrade

If a downgrade leaves too many active members or projects, the organization enters a computed read-only state. Renewal, member deactivation, and project deletion remain available, and normal writes recover automatically once usage is within the limit. Excess Workbooks block only the creation of another Workbook. Owners and Admins can set the current project’s monthly credit quota under Organization → Projects → Edit. Leaving it empty uses the shared organization pool. Reaching the quota blocks credit-consuming actions only in that project; other projects can continue using the organization pool.

​
View usage

In Cloud, Owners, Admins, and Billing Admins can open Organization → Usage to view:
  • the current-cycle overview;
  • usage grouped by project or actor, with an independent range of the last 24 UTC hours, 7 days, or 30 days;
  • chart and detail views of the same aggregate data; the actor view distinguishes members, API keys, system usage, and pre-migration billing attribution.
Self-hosted deployments do not provide an organization usage page. API keys remain project-scoped. The organization usage page does not provide a cross-project API key list; create, review, or deactivate keys from the relevant project’s settings. Historical records without a known real actor are labeled Pre-migration billing attribution instead of impersonating a member.