Skip to main content
Switch to the account you want to view and open Capacity from the account menu. Usage is divided into Resources and Services.

​
Plans and billing

Plans are being redesigned. The following details will be added when the new functionality is finalized:
  • TODO: Plan types and included resource and service quotas.
  • TODO: Subscription, plan change, and payment steps.
  • TODO: Billing periods, prices, and usage billing rules.

​
View resource usage

Resources shows allocated capacity and limits for table count, table storage, and Notebook CPU and memory. Tables continue to occupy capacity while retained. Notebook CPU and memory are allocated while an instance runs and released when it ends.
Table capacity and Notebook CPU and memory usage

​
View service usage

Service usage measures the load that operations place on underlying services. Services shows current usage and capacity limits. Usage above the account’s service capacity may be throttled depending on platform load.

​
OpenAPI units

OpenAPI calls are billed in units: each call costs max(100, function execution milliseconds), and queue wait time is excluded. Units are charged when the function returns successfully and when the function itself raises an error; platform-side failures are not charged. An account holds two balances. monthly_units resets each month and is spent first; addon_units is purchased separately and covers the remainder. When the two together fall below 100 units, calls are rejected. To check the remaining units, see Authentication.