Skip to main content
Limits apply to the organization as a whole, across every member, API key, CLI, SDK, dashboard, and CI job. They are safety defaults rather than pricing tiers and can be reviewed individually.

​
Organization defaults

Sandbox creates from the dashboard, CLI, SDK, snapshot restores, and run.cloud CI all use the same sandbox, CPU, and memory budgets. Whichever limit is reached first blocks additional creates with 429. Destroy sandboxes you no longer need to release their capacity. Sandbox count, reserved CPU, and reserved memory defaults can be raised per organization by run.cloud operators (for example for large concurrent agent fleets). Prepaid credit increases the unpaid-usage ceiling. An organization owner can set a lower spend limit from the billing dashboard; when that customer-set limit is lower, it becomes the effective ceiling. Reaching the effective ceiling blocks new resources and stops active sandboxes and simulator sessions.

​
Request a higher limit

Email [email protected] from an address associated with your organization. Include:
  • your organization name or ID;
  • the limit you want raised and the requested value;
  • the workload and expected duration;
  • when you need the additional capacity.
We will review available capacity and billing status, then confirm the limit and when it takes effect. For planned launches or large temporary bursts, contact us before the workload starts so we can reserve capacity.