Vercel Drives, persistent storage for sandboxes, reaches GA
A drive is storage you mount into a Vercel Sandbox that survives after the sandbox stops, so an agent or a dependency cache can pick up where it left off.
Vercel made Drives generally available for Vercel Sandbox on 15 October. A drive is a storage volume you mount into a sandbox as a working directory. Files written to it persist after the sandbox stops, and a later sandbox, even a different one, can mount the same drive and continue from where the last run left off.
Drives default to 1 TiB of storage, or 1 GiB on the Hobby tier, with a 16 TiB maximum quota available on request. A sandbox can mount up to four drives at once. Only one sandbox at a time can mount a drive read-write, but you can share it read-only across many sandboxes using snapshots. Storage is billed at $0.05 per GB-month, plus separate charges for reads and writes.
const drive = await Drive.getOrCreate({ name: 'shared-deps' });
const sandbox = await Sandbox.create({ mounts: { '/cache': drive } });
Why it matters: an agent whose work spans multiple sandbox runs, or a build pipeline that reinstalls the same dependencies every time, used to need its own plumbing to carry files between environments. Mounting a drive turns that into a couple of SDK calls, which matters more as coding agents move from one-shot tasks to longer-running jobs.