Botperch

CapabilitiesSnapshots and forks

Automatic backups

The provider takes backups for you on a schedule.

Short answer: 3 of 16 providers offer it fully: Agent 37, Runtime and boxd. With a catch: Boat, Cloudflare Sandbox, Sandboxer, Tensorlake and Vercel Sandbox. Checked 29 October 2026.

3 yes5 with a catch8 no0 not publishedChecked 29 October 2026

Who offers it

Part of Snapshots, forks and templates, which explains why it matters.

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

  • Agent 37YesNightly; 7 slots

    Note: Covers only /home/node, and a restore puts the files back in place.

    docs-confirmed “Every instance’s data (`/home/node`) is backed up nightly into seven rotating slots, so the last seven nights are available as restore points.” Source

  • boxdYes

    Note: Off by default; you turn a schedule on for each machine.

    docs-confirmed “A backup uploads a machine’s **disk** to object storage, off the cluster, for disaster recovery. Backups are off by default and set per machine.” Source

  • RuntimeYesDaily, or your cron

    Note: Backups cover volumes only; a sandbox's own disk has no copy.

    docs-confirmed “A volume is backed up off its server every day, and whenever you ask.” Source

  • BoatWith a catchEvery minute

    The catch: These are automatic snapshots kept with the machine, not an off-site backup, and only the newest one is kept, so there is no history to go back through.

    docs-confirmed “boat, every minute and at each stop” Source

  • Cloudflare SandboxWith a catchOn stop, 30 days

    The catch: A snapshot can be saved automatically when a sandbox stops, but there is no schedule and snapshots expire after 30 days.

    docs-confirmed “To save a sandbox each time it stops for inactivity, refer to [Save a sandbox automatically](/sandbox/files/save-a-sandbox-automatically/).” Source

  • SandboxerWith a catchEvery 10 minutes

    The catch: These are automatic snapshots kept on the same host as the machine, not an off-site backup, so they do not survive losing that host.

    docs-confirmed “**Continuous snapshots** (disk) | Every 10 minutes while a sandbox runs, and at every stop” Source

  • TensorlakeWith a catch

    The catch: Only the storage you mount is saved automatically; a machine's own disk has no copy.

    docs-confirmed “An **autosave checkpoint** is a durable, shared recovery point for the mounted file state.” Source

  • Vercel SandboxWith a catchOn every stop

    The catch: A copy is saved each time the machine stops, but there is no schedule and only the last few are kept.

    docs-confirmed “snapshots are created automatically whenever a session stops, and the next session resumes from the most recent snapshot” Source

  • BlaxelNo

    Standby snapshots are for fast resumes, not for disaster recovery; there is no backup schedule.

    inferred “Automatic deletion differs from the automatic standby (*scale-to-zero*) which happens to **all sandboxes** when inactive and where the memory and filesystem are snapshotted to be resumed instantly.” Source

  • DaytonaNo

    Snapshots are taken when you ask; there is no backup schedule.

    inferred “Snapshots are persistent, point-in-time captures of sandbox state” Source

  • E2BNo

    No automatic backup schedule; snapshots are taken when you ask.

    inferred “You can list all snapshots. The method returns a paginator for iterating through results.” Source

  • InstaBoxNo

    No backup schedule; snapshots are taken when you ask.

    inferred “Save a machine once, start new ones from it.” Source

  • LizardNo

    No backup schedule; snapshots are taken when you ask.

    inferred “A snapshot holds the same, and you can restore it after the source sandbox is gone.” Source

  • MorphNo

    No backup schedule; snapshots are taken when you ask.

    inferred “Snapshots are immutable point-in-time copies of both memory and disk state.” Source

  • SpritesNo

    No backup schedule; persistence covers pauses, and checkpoints are manual.

    inferred “Persistence keeps your filesystem across pauses on its own” Source

Related

Other capabilities in this feature

Where it decides the choice

The feature

Words used here

  • SnapshotA saved copy of a machine at one moment, so it can be restored or copied later. Some providers save memory and running programs too, others only files.
  • ForkStarting one or more new machines from a snapshot, each continuing from the same point. Useful for trying several things in parallel.

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