Billing and plans
Review plan usage and limits, change subscriptions safely, and manage billing details and invoices.
Loading documentation…
Powered by heyo
An organization's plan controls its capacity and some product capabilities. Prices, quotas, and plan contents can change; use the console's Plan/Quotas page and checkout confirmation as the source of truth.
The console shows current use and remaining headroom for applicable limits, which can include:
Do not rely on fixed counts from documentation or another organization. Check capacity before adding a resource or starting an extra manual run.
Open Plan/Quotas as an organization Owner. Review the current price, billing interval, included capabilities, and limits shown for each option.
Before a lower-cost or smaller plan, review the impact dialog carefully. Resolve any resources or schedules that exceed the target plan.
The final console confirmation is authoritative. Upgrades generally take effect immediately with prorated billing; cheaper changes generally take effect at the end of the current period.
Reopen Plan/Quotas, confirm usage and effective limits, and check that important workers and schedules remain active.
Existing resource counts can exceed the target limits, and hourly schedules can be incompatible with a daily minimum cadence. A target plan can also remove reporting access or remove audit-log entitlement and retained audit-log data. Review the specific overages and feature losses in the impact dialog, adjust incompatible schedules, and preserve required records before confirming.
Owners can open the Customer Center from the billing area to manage customer and payment details and access invoices. Other organization roles cannot manage billing.
If a quota blocks an action, remove unneeded resources, wait for a period-based allowance to renew where applicable, or choose a plan with suitable capacity. Pausing a resource does not free a numeric resource quota. Raising a plan limit does not guarantee worker compute, source availability, or successful checks; those remain separate operational requirements.