Product - Sandboxes

why runloop

Devboxes, Blueprints, Snapshots, Tunnels, and Mounts

Sandboxes is the Execution primitive, the foundation every other Runloop primitive runs on. A devbox is a hardware-isolated micro-VM with a full Linux environment: filesystem, shell, networking, and persistent state. Blueprints define and pre-build the environment as a reusable image. Snapshots checkpoint disk state for branching and restore. Tunnels expose ports publicly or behind a token. Mounts attach code, agents, files, S3 objects, or Axon brokers.

Text button?

SEACTION FEATURE

Feature Block Alternating

Run structured benchmarks and compare models before deploying to production.

Blueprints

Build the Environment Once, Boot Devboxes From It Forever

A blueprint is your devbox environment as code: a Dockerfile, system setup commands, code mounts, build args, secrets, named contexts, and network policies. The platform builds it (QUEUED, PROVISIONING, BUILDING, SUCCESSFUL) and stores the image, so every devbox launched from that blueprint boots from a warm cache.

Sub-second cold start — apt, pip, clone, build all happen once at blueprint build time, not on every devbox.

Versioned and inheritable — blueprints reference base blueprints; each update is a new immutable image.

Build from inspection — create blueprints from an existing devbox's installed state, not just from a Dockerfile.

Same blueprint, every primitive — agent workloads, benchmark scenarios, and production runs all launch from the same image.

Find Out More

Snapshots

Branch, Resume, and Fork Devbox State

A snapshot captures the full disk state of a devbox. You can launch a new devbox from any snapshot, fork the same checkpoint into parallel devboxes, or roll a devbox back. Snapshots flow through their own state machine (QUEUED, PROVISIONING, SNAPSHOTTING, SUCCESSFUL) and are first-class through both sync and async APIs.

Parallel exploration — snapshot a working agent, then fork the same point into many devboxes to try different approaches.

Training-loop efficiency — restore from snapshot at each fine-tuning step instead of rebuilding environments from scratch.

Rollback to any point — promote a working snapshot to production, roll back instantly if a regression appears.

Sync or async — small snapshots return synchronously; large ones run in the background and notify on completion.

Lifecycle

Suspend Between Work, Resume on Demand, Burn No Compute

A devbox is not just an ephemeral container. It moves through a state machine, provisioning, initializing, running, suspending, suspended, resuming, shutdown, that you control through the lifecycle API. A suspended devbox holds its full state and costs nothing in compute. Combine with wake_on_http and a tunnel call resumes the devbox automatically.