Understand plans and usage

Current cloud tiers are Builder, Pro and Business, with Custom arrangements for other requirements. In Pricing (opens in a new tab), each bundle combines a cloud subscription with optional recurring AI credits and development-machine hours. AI and machine refills can be selected independently; review the displayed price and renewal total.

A cloud-only bundle can run deployed resources without including new machine hours or platform AI credits. You may use purchased balances, add eligible top-ups, or use an external coding client through the authenticated product MCP. Starting a Rumata development machine still needs its own available hours and capacity.

Your projects share the billing account’s allowances. An invitation grants permissions, not another subscription or another usage pool. A no-plan account is not a free development plan: it cannot build or run applications until the required subscription and resources are active.

Included consumable allowances reset at their displayed paid-period boundary and do not roll over. Active capacity and allocated storage differ from period consumption: stopping compute does not necessarily free retained storage.

1. Open Usage (opens in a new tab) and confirm the billing account shown.
2. Find the resource named in the operation or error. Expand All plan allowances and inspect its used, remaining, capacity and period values.
3. Distinguish consumed allowance from concurrent reservations and currently retained resources.
4. Check the billing period and separately purchased balances or capacity expiry before comparing totals.

An overview metric is an observation, not permission to run work. An operation can be authorized but blocked by resource admission; it can also have allowance remaining but fail an application or dependency check.

1. Read the exact resource and reason before retrying.
2. For a period allowance, wait for its reset or purchase an available top-up. For concurrency, stop an unused workload when safe.
3. For storage, inspect used bytes and reserved capacity. Deleting a file does not automatically shrink its reservation; retained workspaces and disks can consume capacity while stopped.
4. Review a bundle change or available resource purchase for the correct billing account.

Self-serve plans do not silently turn exhausted allowance into unlimited paid overage. Read, export and recovery access can differ from write/start access. A limit is not a request to delete data; cancellation, retention and purge are separate lifecycles.

Resource purchases distinguish one-time from recurring. Purchased consumable balances do not expire when the included monthly allowance resets. Capacity and storage purchases have their own paid term; stopping recurrence preserves the already-paid term. Review the specific offer rather than applying one expiry rule to every resource.

Switching a bundle changes its included refills; an infrastructure-only upgrade preserves existing AI and machine refill selections. Separately purchased recurring extras remain separate. Review the immediate charge estimate, next renewal amount and effective date before confirming. Increases can be prorated; removals and downgrades normally start at renewal.

After checkout, wait for confirmed payment and activation. If the account reports pending, use the payment-status control or contact Support before paying again. See Billing controls.