CapabilitiesStorage
One volume, several machines
Several machines can use the same storage at once.
Who offers it
Part of Storage: disk, volumes and what persists, which explains why it matters.
Fully: Daytona, Modal and Tensorlake. With a catch: Blaxel, Cloudflare Sandbox, E2B, Morph, Runtime and Vercel Sandbox. Not at all: Agent 37, Boat, boxd, InstaBox, Lizard, Sandboxer and Sprites.
- DaytonaYes
Note: Writes are not transactional, so two machines writing one file means the last write wins.
docs-confirmed “a single volume can be mounted to multiple sandboxes” Source
Note: Two machines writing the same file means the last write wins.
docs-confirmed “it supports more files, higher throughput, concurrent writes from hundreds of containers” Source
- TensorlakeYes
Note: Same-path writes are last-writer-wins, so two machines editing one file can clash.
docs-confirmed “Disjoint paths merge automatically, same-path writes are last-writer-wins.” Source
- BlaxelWith a catch
The catch: Shared storage is a separate product called Agent Drive; a volume itself serves one machine at a time.
docs-confirmed “At this time, you can only attach one volume to a sandbox. A volume can also only be attached to one sandbox at a time.” Source
- Cloudflare SandboxWith a catch
The catch: The shared option is a bucket, not a disk, so files are not locked and two machines can overwrite each other.
docs-confirmed “Share job inputs and outputs with other systems | [Mount an R2 bucket](/sandbox/files/mount-an-r2-bucket/) | Renames, locks, and permissions do not work as they do on a local disk” Source
- E2BWith a catch
The catch: One volume can serve several sandboxes, but volumes are in private beta.
docs-confirmed “Persistent storage that exists independently of sandboxes and can be mounted across multiple sandboxes.” Source
- MorphWith a catch
The catch: Sharing happens through an S3 bucket, not a disk several machines mount.
docs-confirmed “Morph Volumes are persistent S3-compatible storage for build caches, release artifacts, checkpoints, and shared datasets.” Source
- RuntimeWith a catch
The catch: Only one machine can write a volume at a time; others can hold a read-only copy taken when they start.
docs-confirmed “**`"rw"`** (the default): read-write, attached to one sandbox at a time.” Source
- Vercel SandboxWith a catch
The catch: Only one machine can write a drive; others get a read-only copy taken when they mount it.
docs-confirmed “Only one sandbox at a time can mount a given drive as read-write: use snapshots for shared access.” Source
- Agent 37No
No storage can be attached to two machines at once.
inferred “The whole disk persists, like a VM.” Source
- BoatNo
No storage can be attached to two machines at once.
inferred “A saved snapshot is a copy of a sandbox disk that you save under a name.” Source
- boxdNo
A disk takes one machine at a time.
docs-confirmed “One attachment at a time. A disk’s storage is opened read-write by the machine that holds it, so a second attachment would be a second writer to the same bytes.” Source
- InstaBoxNo
A disk belongs to one machine.
inferred “A machine has one disk, `/data` (home is `/data/home`), 20 GiB by default.” Source
- LizardNo
A volume serves one sandbox at a time.
docs-confirmed “Each volume mounts at **`/workspace`** and attaches to **one sandbox at a time**.” Source
No storage can be attached to two machines at once.
inferred “"Disk" is space for your files, added on top of the OS image” Source
- SpritesNo
Storage belongs to one Sprite.
inferred “The split is simple: disk persists, memory does not.” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.