Sandbox persistence is now GA

now automatically save and restore filesystem state between sessions. Persistence is on by default, meaning no snapshots to manage or state to track manually. Vercel SandboxesEach sandbox has a durable, 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. customizable nameWhen you call , persistence is enabled by default:Sandbox.

create() Each automatic snapshot consumes , which is billed separately from compute. For ephemeral workloads, opt out of persistence to minimize storage costs:snapshot storageTo opt out of persistence with the CLI, pass to . Non-persistent sandboxes discard their filesystem when the session ends. --non-persistentsandbox createResuming is automatic. Any call on a stopped sandbox, like or , starts a new session from the most recent snapshot.

runCommand()writeFiles()Upgrade to the latest version to create persistent sandboxes by default: Learn more about persistent sandboxes in the . documentationRead moreCreate a persistent sandboxResume a persistent sandboxOther improvementsGet started : Create a new sandbox from an existing oneSandbox. fork(): Idempotent retrieve-or-create for long-lived sandboxesSandbox. getOrCreate(): Permanently delete a sandboxSandbox. delete()Richer : Returns snapshot metadata plus active-CPU and network-transfer totalssandbox.

stop()Lifecycle hooks: and hooks for , , and onCreateonResumecreategetgetOrCreate: Assign custom properties to sandboxes for multi-tenant trackingTagspnpm install @vercel/sandbox@latest # SDKpnpm install -g sandbox@latest # CLI