Vercel Sandbox is now available in all regions

Vercel Sandbox is now accessible across all 20 of its compute regions, an expansion from the previous four. This change allows teams to run sandboxes closer to databases, storage, and other services, which helps lower latency for development and testing workflows. The move also supports compliance with data residency and regional processing mandates by enabling workloads to remain within approved geographic boundaries. The default region remains iad1, but teams can select alternatives during setup.

Teams on Pro and Enterprise plans gain additional control by configuring failover regions for sandboxes. If Vercel cannot provision a sandbox in the primary region, it automatically attempts each failover region in sequence until successful. This feature is particularly useful for organizations with strict data residency policies, as it allows them to restrict both primary and failover regions to pre-approved locations. The failover mechanism operates transparently, ensuring minimal disruption to development processes.

Users can set a default region for new sandboxes through the project’s Settings under Sandboxes, streamlining the selection process for future deployments. The region can also be specified at creation time using either the Sandbox SDK or CLI, overriding the project default. Existing sandboxes will continue running in the regions where they were originally created, maintaining continuity for ongoing projects.

Active CPU and Provisioned Memory rates vary depending on the selected region, and pricing details are available in the Sandbox pricing documentation. Users of the Sandbox SDK or CLI must update to the latest version before selecting one of the newly supported regions to ensure compatibility. Additional guidance on region selection, failover configuration, and CLI setup is provided in the Sandbox regions documentation.