RAM-speed storage, snapshots that never expire.

Each sandbox filesystem runs in memory for unbeatable performance on almost every operation. Filesystem snapshots persist until you choose to delete them, so a suspended sandbox restores its files exactly as they were.

Read the filesystem docs Explore sandbox architecture
An open storage well with files inside, one written by an agent

Sandbox filesystem layering

  • tmpfs (Writable Layer) RAM Speed (Write)
  • EROFS (Base Image Layer) Read-Only Base 
01sandbox = (02    Sandbox.debian_slim()03    .with_memory(04        "vol-4f2a17",05        "vol-9c02bb",06    )07)08@agent.task(sandbox=sandbox, region="us-west-2")09def run():10    ...

[TECHNICAL DEEP DIVE]

Why it runs in memory

Blaxel keeps the writable layer of every sandbox in RAM. Your image sits in a read-only base, an in-memory layer takes every write, and the two are stitched together transparently, so reads and writes land at memory speed. The agent sees one ordinary filesystem and never has to think about where the bytes live.

  • Writes hit RAM

    The working layer lives in memory, so file operations stay fast.

  • Read-only base

    Your image is served from an efficient read-only layer underneath.

  • One seamless filesystem

    The layers are merged transparently for the agent.

[SUSPEND WITHOUT LOSING A BYTE]

Snapshots that persist until you delete them.

When a sandbox goes idle, Blaxel snapshots the entire state, the full in-memory filesystem and every running process, and parks it. Reconnect and it restores in under 25 milliseconds, with files and processes exactly as they were. The snapshot stays until you delete it, so there is no expiry to manage.

  • Files and processes

    The snapshot captures the whole filesystem and running work, not just data at rest.

  • Sub-25ms resume

    A suspended sandbox comes back almost instantly.

  • No expiry

    Snapshots persist until you choose to remove them.

When to add a volume

In-memory storage is built for speed, and roughly half of a sandbox's memory is reserved for it. When a workload needs more room than memory allows, or data that must outlive the sandbox itself, attach a volume. Volumes trade some speed for durable, redundant capacity.

Explore Volumes

In-Memory Storage

Default
  • Near-zero latency with RAM performance
  • Captures entire process state automatically
  • Size capped at half of sandbox memory allocation

Persistent Volumes

Optional
  • Infinite storage bounds regardless of RAM
  • Outlives the lifecycle of the sandbox container
  • Normal SSD-level throughput speeds

Get started

Spin up your first sandbox in under a second. Up to $200 in credits, no credit card required.

Get started on Blaxel Get a demo
  • Managed cloud
  • Self-hosting
  • VPC