What happened
Vercel Sandbox — the company's isolated execution environment for running AI-generated and untrusted code — is now available in four regions: Washington D.C. (iad1, the default), San Francisco (sfo1), Cleveland (cle1), and Paris (cdg1), with broader regional coverage planned. Region selection is available on every pricing tier, and Pro and Enterprise teams can additionally configure failover regions so a sandbox workload automatically shifts if its primary region goes down. Updated SDKs and CLI tooling let teams pin a project, or an individual sandbox, to a specific region.
Why it matters for your business
Teams building agentic coding tools, AI app builders, or any workload that executes untrusted code now have a practical lever for latency: placing sandbox execution close to the databases and object storage it talks to. For regulated or uptime-sensitive products, the failover option is the more consequential change — a sandbox outage in one region no longer means a hard stop, provided the team has planned for it on a Pro or Enterprise plan.
What to watch next
Vercel says support for its full region list is coming, which will matter most for teams outside North America and Europe. Snapshots stay locked to the region they were created in, so teams standardizing on Sandbox for CI or agent workflows should pick a home region now rather than after usage scales.