Skip to main content
Agent Sandbox applies quota limits to a team. The quotas cap how many sandboxes run at once, how long a sandbox can live, and the vCPU, memory and local storage a single sandbox can have. The current values are on the AGENT SANDBOX › Quotas & Limits page of the console.
Install the SDK, or the CLI for ppio commands, and set the PPIO_API_KEY and PPIO_DOMAIN environment variables before running these examples. See Quickstart and Install and authenticate.

Quota items

Maximum Concurrent Sandboxes

The number of sandboxes that run at the same time.

Sandbox Maximum Lifetime

The maximum timeout one sandbox can have; long-running mode lifts the cap.

Maximum vCPU per Sandbox

The vCPU cores a single sandbox can use.

Maximum Memory per Sandbox

The memory a single sandbox can have.

Maximum Local Storage per Sandbox

The runtime storage available to a single sandbox.
Total vCPU and memory in use across running sandboxes are also limited (concurrentVcpu, concurrentRamMb).

Tiers

The quotas depend on the tier of the team.

Free

The default tier for a new team.

Paid

Available after adding balance or enabling a credit line.

Enterprise

For teams that need custom limits and dedicated support.

Configuration rules

CPU and memory are set when the template is built, and the configuration must meet these requirements:
  • vCPU must not exceed the maximum vCPU of the tier.
  • vCPU must be a whole number.
  • Memory must not exceed the maximum memory of the tier.
  • Memory is configured in fixed increments, within a range of memory allowed per vCPU.
  • The final configuration is set by both the tier maximums and the allowed memory per vCPU.
If the requested resource configuration exceeds the quota of the tier, the request fails. If a region has no available capacity, sandbox creation can fail even when the team quota is not used up.
Choose CPU and memory for the workload to avoid running out of memory or using resources unnecessarily.

Check limits and request an increase

1

Read the current limits

Open the AGENT SANDBOX › Quotas & Limits page of the console. Each quota appears as a row with its Current Limit.
2

Request a higher limit

In the row to raise, select Increase Limit.
The control appears only for a team member with permission to change quotas, and only on rows that can be adjusted; the other rows show a dash in the Actions column.
3

Submit the request

In the Request Rate Limit Increase dialog, enter the requested limit, a reason and a contact email, then select Submit.
Higher limits can also be requested from PPIO support. Enterprise quotas can be customized.

Query the current quota with the SDK

The SDK returns the limits that apply to the team and the resources in use. Run it before launching a large batch of sandboxes, or when a create call fails on quota.

Quota response fields

The quota response includes limit and usage objects.
object
Limits that apply to the team.
object
Resources currently in use.
usage.concurrent_instances (Python) / usage.concurrentInstances (Node.js) shows how many sandboxes currently count toward the concurrency limit.
Quota usage is intended for capacity planning and troubleshooting. Usage data can arrive with a short delay that depends on the backend reporting path.
Last modified on November 19, 2026