Vercel Drives Reaches General Availability for Vercel Sandbox

What a Drive does

According to Vercel, a Drive is persistent storage that you mount as a directory in a Vercel Sandbox. Its files remain available after the sandbox stops. Later runs and other sandboxes can then access the same files by mounting the same Drive.

Vercel names several uses for this. Teams can preserve an agent's workspace or file-based memory across runs. They can also make datasets, models, dependencies and build artifacts available across multiple sandboxes, instead of preparing them again each time.

Forking Drives for parallel work

Drives can also be forked into independent writable Drives. According to Vercel, forks inherit the source Drive's data, region and maximum size, and then store their own changes.

This means parallel workers can start with the same files and make changes without affecting the original Drive or one another. Vercel describes the pattern as starting parallel workers from the same saved workspace while keeping their changes isolated.

The code example in the announcement uses the @vercel/sandbox package, which exports both Sandbox and Drive. It retrieves an existing Drive named base-drive, then loops twice. In each pass it forks the Drive under a name such as worker-0, creates a sandbox that mounts the fork at /data, runs the session and then deletes the fork.

Availability and what it means

The general availability release covers Vercel Sandbox on Hobby, Pro and Enterprise, so the feature is not limited to a single paid tier. Vercel points to its Drives documentation for further details.

For developers running agents or batch jobs in sandboxes, the change addresses a practical limit: a sandbox's local files otherwise disappear when it stops. With Drives, a workspace can be saved and reused, and forks give each parallel worker its own writable copy to work from.