Sandbox guide

CapabilitiesStorage

Files survive a stop

Stopping the machine keeps its disk; starting it again finds the files where they were.

10 yes1 with a catch5 no0 not published

Who offers it

Part of Storage: disk, volumes and what persists, which explains why it matters.

Fully: Agent 37, Blaxel, Boat, boxd, Daytona, InstaBox, Runtime, Sandboxer, Sprites and Vercel Sandbox. With a catch: Tensorlake. Not at all: Cloudflare Sandbox, E2B, Lizard, Modal and Morph.

  • Agent 37Yes

    Note: The disk bills at $0.09 per GB-month until you delete the instance.

    docs-confirmed “The whole disk persists, like a VM.” Source

  • BlaxelYes

    Standby keeps everything; archive keeps the files and restarts processes with new IDs.

    docs-confirmed “Unarchiving it starts the sandbox again from its image and writes the archived filesystem back over it, so you get the same sandbox back with its files.” Source

  • BoatYes14 days

    Note: The disk is deleted 14 days after a stop unless you saved it.

    docs-confirmed “Boat keeps the snapshot of a stopped sandbox for 14 days.” Source

  • boxdYes

    A stop keeps the disk; standby and hibernate keep memory as well.

    docs-confirmed “A machine can go to sleep in place and wake on demand.” Source

  • DaytonaYes

    The whole disk persists and bills while stopped.

    docs-confirmed “The filesystem and memory state are preserved, and CPU is no longer consumed.” Source

  • InstaBoxYes

    The /data disk and the template’s root disk are kept on stop.

    docs-confirmed “The root disk and `/data` are kept; processes and memory are not.” Source

  • RuntimeYes

    Note: A stopped disk is billed and kept until you delete the sandbox.

    docs-confirmed “A stop keeps the disk.” Source

  • SandboxerYes

    A stopped sandbox costs nothing and keeps everything.

    docs-confirmed “A stopped sandbox costs nothing and keeps everything.” Source

  • SpritesYes100 GB

    The disk persists; memory does not.

    docs-confirmed “The split is simple: disk persists, memory does not.” Source

  • Vercel SandboxYes

    Persistence is the default for new sandboxes.

    docs-confirmed “Persistence is the default.” Source

  • TensorlakeWith a catch48 h after terminate

    The catch: A terminated machine can be brought back for 48 hours; after that its files are gone.

    docs-confirmed “Call `restart` within 48 hours of termination to boot it again under the same ID and name” Source

  • Cloudflare SandboxNo

    The disk is deleted with the instance; only a snapshot keeps the files.

    docs-confirmed “An instance runs only until something stops it, and its processes and the files on its disk end with it. The next `start()` creates a new instance.” Source

  • E2BNo

    Killing a sandbox ends it; files survive only in a snapshot or a volume.

    inferred “By default a pause saves **both** the filesystem and the memory.” Source

  • LizardNo

    A stop deletes the disk; only /workspace on a volume and your snapshots remain.

    docs-confirmed “A stop (kill or expiration) deletes the sandbox's disk” Source

  • MorphNo

    A stop releases everything; the files come back only from a snapshot.

    docs-confirmed “**Stop** : Use when you're completely done with the instance and want to release all resources.” Source

Related

Other capabilities in this feature

Where it decides the choice

The feature

Words used here

  • DiskWhere files are kept. On some providers the disk survives a stop, on others it is wiped, which is why the guide asks whether files must be kept.

Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.