Drives for Vercel Sandbox in Private Beta

Vercel launched Sandbox Drives in private beta, offering persistent, attachable storage with a lifecycle independent from any sandbox. Users can create a drive once and mount it at a configurable path across multiple sandbox sessions, with data remaining available after the sandbox stops. The feature enables retaining agent workspaces, cloned repositories, and build outputs across disposable sandboxes, though drives are limited to read-write access by one sandbox at a time during the beta period.

Vercel Sandbox https://vercel.com/docs/sandbox now supports drives in private beta. Drives are persistent, attachable storage with a lifecycle independent from any sandbox. Create a drive once, then mount it at a configurable path when starting a sandbox. When the sandbox stops, the drive remains available to attach to a later sandbox. Install the beta SDK https://vercel.com/docs/sandbox/sdk-reference @vercel/sandbox@beta or beta CLI https://vercel.com/docs/sandbox/cli-reference sandbox@beta , then create and mount a drive: Sandbox Drives are useful for: Keeping agent workspaces across disposable sandboxes Retaining cloned repositories, dependencies, and build outputs Managing data independently from the sandbox lifecycle During the private beta, a drive can be mounted read-write by one sandbox at a time. Sandbox drives should not be used for production data while in private beta. Sign up here https://vercel.typeform.com/to/F19n6v2q to join the waitlist, and learn more in the docs https://vercel.com/docs/sandbox/concepts/drives .