Vercel Sandbox now supports persistent storage via Drives, currently in private beta. A Drive exists independently of any sandbox lifecycle: create it once, mount it at a configurable path when a sandbox starts, and it survives after the sandbox stops.
The use cases are concrete: preserving agent workspaces across disposable sandboxes, retaining cloned repositories and build outputs, and managing data outside the sandbox lifecycle. Install the beta SDK at @vercel/sandbox@beta or the beta CLI at sandbox@beta to start. The current constraint worth knowing: one sandbox can mount a drive read-write at a time, and Vercel explicitly warns against using Drives for production data during this phase.
The full docs detail the mount path configuration and SDK reference, which is where the implementation specifics live. Sign up at the Vercel typeform to join the waitlist. The lifecycle-independent storage model is the thing to watch: it suggests Vercel is building toward more stateful, persistent compute on top of what started as ephemeral sandbox infrastructure.
[READ ORIGINAL →]