Vercel Sandbox creation now returns a ready sandbox
Vercel Sandbox.create() now blocks until ready—50ms slower at p50, but eliminates wait-and-retry patterns in the first operation.
Why it matters
A developer-experience improvement for serverless sandbox operations: creation now includes snapshot restoration time, so the first command or file I/O no longer stalls. The tradeoff is baked into creation latency rather than spread across the first operation.
The key facts
11 to knowSandbox.create() now resolves only after snapshot restoration completes
Creation is ~50ms longer at p50 latency for cached snapshots; larger increase possible for uncached snapshots
Total time through first operation remains the same (latency shift, not added cost)
Startup errors now reject Sandbox.create() instead of surfacing during subsequent operations
Change is automatic; no SDK upgrade or configuration required
Published October 8, 2026
First command or file operation no longer waits for snapshot restore
Startup errors now reject create() instead of surfacing during operations
Creation time increased ~50ms at p50; larger increase possible for uncached snapshots
Total time through first operation remains unchanged
Change applies automatically; no SDK upgrade or configuration required
Go to the source
Vercel Blogvercel.com
Publisher excerpt: A new Vercel Sandbox is now ready to run commands and read or write files when creation completes. now resolves only after snapshot restoration completes, so the first command or file operation no longer waits for it. Startup errors also reject instead of surfacing during that…