Vercel Sandbox goes multi-region — pick where your agent code runs
Four regions and per-sandbox failover ship alongside write-only Secret env vars and a fix that stops cached builds from being downgraded.
Copy markdown
Pin your sandboxes to four regions
Vercel Sandbox is now generally available in iad1, sfo1, cle1 and cdg1, with a per-sandbox region choice, project defaults, and configurable failover regions. If you run agent-generated or untrusted code in Sandbox, you can cut round-trip latency, keep execution in-region for data residency, and fail over to another region instead of going dark when one is degraded.
Env vars now split into Config and Secret
Adding an environment variable now forces a choice: Config values stay readable to authorized team members, while Secret values become write-only the instant you save. It's a one-dialog change with real blast-radius reduction — a compromised dashboard session or a curious teammate can no longer read your API keys back out.
Cached builds stop getting downgraded
Elastic Build Machines now read Turborepo cache hits before deciding a machine-tier downgrade, so a project that builds fast only because it's cached no longer gets bumped to a weaker tier and then stalls the moment the cache misses. If your CI times swung wildly build-to-build, this is the fix.