Vercel Sandbox is now available in all regions
- Source
- vercel.com
- Author
- Marc Codina Segura
- Date
Vercel expanded Sandbox, its code-execution environment built for running agent-generated code, from 4 regions to all 20 of its compute regions. The update adds configurable failover regions and SDK and CLI support for picking a region at creation time, rather than accepting whatever region Vercel assigns by default. For teams running agent code that needs to sit close to a specific data store or meet a data-residency requirement, this removes a constraint that previously forced a choice between using Sandbox and keeping compute near the data it touches. Failover region configuration also means a sandbox workload can keep running through a regional outage without the calling application handling that logic itself. The practical effect is that Sandbox becomes viable for a wider range of production agent workloads, not just prototypes, without switching to a different code-execution provider to solve for latency or residency.
Context
Vercel expanded execution from four compute regions to twenty, giving teams more choice about where code runs relative to its databases and storage. Region selection is available on every plan. Pro and Enterprise teams can also specify an ordered list of fallback regions: if creation fails in the primary region, the service tries the alternatives in sequence. Teams with geographic processing requirements therefore need to consider both the primary location and the fallback list. Existing sandboxes stay where they were created; a new regional default affects new instances. Region announcement.
- sandbox — An isolated environment where AI-generated code or agent actions run without being able to touch anything real.
“If Vercel can't create a sandbox in the primary region, it tries each configured failover region in order.”
“A region passed at creation overrides the project default.”
Checking sign-in…
Loading comments…