Introducing Vercel Drives: persistent storage for agents
By Steven Van ·
Drives are generally available for Vercel Sandbox, with read-write mounts, read-only snapshots and forks, on Hobby and Pro plans.
Agents can now keep their files on a drive that lives separately from the sandbox running them. Vercel made Drives generally available for Vercel Sandbox, as described in its guide. A new sandbox that mounts the same drive finds the repository and anything else the agent wrote, even if it uses a different image, runtime or compute.
Persisting a workspace
A drive is created once, then mounted at an absolute path such as /workspace when a sandbox is created. It works from the CLI (sandbox drives get-or-create and sandbox create --mount) or from the Sandbox SDK with Drive.getOrCreate(). Everything written under the mount path stays on the drive. Everything outside it belongs to the sandbox.
Each drive belongs to one Vercel project and one region. The region and maximum size are fixed after creation. A sandbox can mount up to four drives, and its region must match the drive's. Only one sandbox at a time can mount a given drive read-write.
Sharing and forking
- Read-only drive snapshots: drive.snapshot() gives a point-in-time view that many sandboxes can mount at once. Later writes to the drive do not appear in an existing snapshot mount.
- Forks: drive.fork() returns a writable copy that starts with the drive's contents. Forks store their own changes and never merge back into the source drive. Forking is also generally available.
Drive snapshots are separate from sandbox snapshots, which capture a sandbox's full filesystem.
Limits and pricing
Drives default to 1 TiB (1 GiB on Hobby), with a default quota of up to 16 TiB. A drive persists until it is deleted. Storage in iad1 on Pro is listed at $0.05/GB-month, plus read and write charges. Drives are supported in both the TypeScript and Python SDKs.