Sandbox persistence is now GA

Vercel Sandboxes now automatically save and restore filesystem state between sessions. Persistence is on by default, meaning no snapshots to manage or state to track manually.

Each sandbox has a durable, customizable name that acts as a unique reference in your project. You can create, retrieve, or resume a sandbox by name. Vercel spins sessions up and down automatically, without interrupting your workflow.

Create a persistent sandbox​

When you call Sandbox.create(), persistence is enabled by default:


Each automatic snapshot consumes snapshot storage, which is billed separately from compute. For ephemeral workloads, opt out of persistence to minimize storage costs:


To opt out of persistence with the CLI, pass --non-persistent to sandbox create. Non-persistent sandboxes discard their filesystem when the session ends.

Resume a persistent sandbox​

Resuming is automatic. Any call on a stopped sandbox, like runCommand() or writeFiles(), starts a new session from the most recent snapshot.

Other improvements​

• 
  Sandbox.fork(): Create a new sandbox from an existing one
  
  
• 
  Sandbox.getOrCreate(): Idempotent retrieve-or-create for long-lived sandboxes
  
  
• 
  Sandbox.delete(): Permanently delete a sandbox
  
  
• 
  Richer sandbox.stop(): Returns snapshot metadata plus active-CPU and network-transfer totals
  
  
• 
  Lifecycle hooks: onCreate and onResume hooks for create, get, and getOrCreate
  
  
• 
  Tags: Assign custom properties to sandboxes for multi-tenant tracking
  

Get started​

Upgrade to the latest version to create persistent sandboxes by default:

• 
  pnpm install @vercel/sandbox@latest # SDK
  
  
• 
  pnpm install -g sandbox@latest # CLI
  

Learn more about persistent sandboxes in the documentation.


Read more

Continue reading...