Drives for Vercel Sandbox now in public beta
Drives provide persistent storage that can be mounted as directories in Vercel Sandbox and reused across multiple sandbox instances. Each Drive supports up to 16 TiB of configurable storage with read/write pricing, enabling users to preserve agent workspaces, datasets, and models across sandbox runs.
Drives for Vercel Sandbox are now available in public beta on Hobby, Pro, and Enterprise.
A Drive is persistent storage that you mount as a directory in a Vercel Sandbox. It isn’t tied to a single sandbox, so you can reuse the same Drive across runs and different sandbox instances.
Use Drives to preserve an agent's workspace or on-disk memory, or to reuse datasets, models, and dependency trees.
Create or retrieve a Drive and mount it at a path when starting a sandbox. Read and write files through the sandbox filesystem at that path.
Anything stored under remains on the Drive after the sandbox stops./data
A Drive supports one read-write mount at a time. After the Drive has been written to, multiple sandboxes can read from it concurrently by mounting point-in-time, read-only snapshots.
Each snapshot reflects the Drive at the moment it's mounted. Later writes aren’t included; mount a new snapshot to access them.
Each sandbox can mount up to four Drives at separate paths. Drives default to a maximum size of 1 TiB (1 GiB on Hobby) and can be configured up to 16 TiB, with higher limits available by request.
Drives are available in every . Each Drive stays in the region where it was created. Sandboxes that mount it must run in that region and can’t use failover regions.Sandbox region
Drive pricing is based on storage, reads, and writes, with rates varying by region. In , storage costs $0.05 per GB-month, reads $0.0015 per GB, and writes $0.004 per GB. Hobby includes 15 GB of Drive storage and 30 GB each of reads and writes per month. See for regional rates and plan details.iad1Sandbox pricing
Learn more in the .Drives documentation
Create and mount a Drive
Share Drive data across sandboxes
Limits and pricing
Source: original entry ↗
More from Vercel
Follow Vercel to get its new changes in your feed and email digest.
Skip sending request bodies to Routing Middleware
Vercel now allows you to skip sending client request bodies to Routing Middleware via the skipMiddlewareRequestBody configuration option, reducing middleware invocation costs and improving time to first byte for requests with large bodies.
Vercel Sandbox creation now returns ready sandbox
Vercel Sandbox instances are now ready to run commands and access files immediately upon creation completion. The Sandbox.create() method now waits for snapshot restoration to finish before resolving, eliminating delays on the first command or file operation.
Step 5 Preview now available on AI Gateway
StepFun's Step 5 Preview model is now available on Vercel's AI Gateway, supporting text and image input with a 1M-token context window optimized for agentic coding, professional knowledge work, and financial analysis. The model can be accessed via the unified AI Gateway API for tracking usage, cost management, and performance optimization.