Vercel Raises Vercel Sandbox Capacity to 10,000 Concurrent Environments.

Vercel is substantially raising the ceiling on its isolated compute service. Vercel Sandbox can now support 10,000 concurrent sandboxes, five times the previous limit, while its vCPU allocation rate can scale as high as 5,000 vCPUs per minute.

The new default quotas apply automatically to Pro and Enterprise teams, according to Vercel’s changelog announcement. Customers do not need to change their configuration or request access.

That increase is aimed at workloads that create many isolated environments in rapid succession. These can include development and testing pipelines, code execution services, and AI agents that need a separate microVM for each task. Vercel Sandbox is also available through Hermes Agent, following a recent integration with Vercel’s AI Gateway and Sandbox.

The most straightforward change is the concurrency limit. Pro and Enterprise teams could previously operate up to 2,000 sandboxes at the same time. That default has now increased to 10,000 concurrent sandboxes.

For smaller development teams, the previous allowance may already have been sufficient. The new limit matters more for platforms running large numbers of automated jobs, especially when each job needs its own isolated environment. A service evaluating generated code, for example, may need to create separate sandboxes for thousands of simultaneous users or agent sessions.

The update does not mean every team will continuously run 10,000 environments. Instead, it gives builders more headroom during traffic spikes, large test runs, or batches of parallel agent activity without first negotiating a custom concurrency limit.

The headline figures are:

• Concurrent sandboxes: increased from 2,000 to 10,000
• Previous vCPU allocation rate: 200 per minute on Pro and 400 per minute on Enterprise
• New vCPU allocation rate: dynamically scales up to 5,000 per minute
• Eligible plans: Pro and Enterprise

The second change is more nuanced. Rather than replacing the previous allocation limits with a fixed 5,000-vCPU allowance, Vercel has introduced a dynamic quota that responds to sustained sandbox creation.

The allocation rate starts at 150 vCPUs per minute. As a team continues creating sandboxes, the permitted rate increases in increments of 500 vCPUs per minute, eventually reaching a maximum of 5,000 vCPUs per minute. Vercel has not provided additional detail in the announcement about how long demand must be sustained before each increase occurs.

This distinction matters for capacity planning. The 5,000 figure is the maximum rate at which compute can be allocated after usage ramps up, not an immediate baseline available from the first minute. It is also an allocation rate rather than a statement that each sandbox receives a particular amount of processing power.

For builders, the dynamic approach should reduce the likelihood that a sudden wave of environment creation hits a rigid provisioning bottleneck. It also lets Vercel expand access gradually as sustained demand becomes clear, rather than reserving the maximum capacity for every team from the outset.

Vercel says teams requiring quotas beyond these defaults can contact its sales team. The company did not announce pricing changes alongside the higher limits, so teams should continue to evaluate usage against the billing terms of their existing plan.

What is Vercel Sandbox?

Vercel Sandbox is a service for running code and commands inside isolated microVM environments. It can be used for development, testing, automated code execution, and AI-agent workloads that need separation between individual tasks.

Which plans receive the new Vercel Sandbox quotas?

The higher default quotas apply automatically to Vercel Pro and Enterprise teams. Vercel says customers that need limits above 10,000 concurrent sandboxes or the stated allocation capacity should contact sales.

Does every team immediately receive 5,000 vCPUs per minute?

No. The dynamic allocation rate begins at 150 vCPUs per minute and increases by 500 vCPUs per minute during sustained sandbox creation, up to a maximum of 5,000 per minute. The announcement does not specify the timing required to reach each higher allocation tier.