Sunday, November 1, 2026

Sandstorm

★3,559Must watch
API

Pack thousands of agent sandboxes on cheap machines by freezing idle ones and waking them on traffic.

Sandstorm

Why it matters

Sandstorm is an open-source (Apache-2.0) Rust control plane from DeepLethe for self-hosted AI agent sandboxes. One binary, sandstormd, can act as master, node, and web console. Idle sandboxes move through hot, frozen, snapshot-on-disk, and detached tiers so memory frees up while wake stays fast. Backends are gVisor containers (default, no KVM) and Firecracker microVMs, each with its own network namespace, schedulable across a fleet.

Agent fleets burn money sitting warm. If you run code-exec, tools, or multi-tenant agents, density is the product: Sandstorm lets one box hold far more sessions than it can keep running, without waiting on a cold Docker start every time work shows up.

How it works

On Linux with cgroup v2 and runsc on PATH, build the console and sandstormd, then run sandstormd serve --master --node. Open the local HTTPS console, sign in with the API token, create a template from an image, and start sandboxes. Scale with scripts/fleet.sh across SSH hosts; nodes join by address or dial out from behind NAT. Wake-on-traffic hits a gateway that restores the sandbox and forwards the request. Everything the console does is also on the HTTP API.

Not a local policy sandbox like Anthropic sandbox-runtime, and not a single-machine Docker wrapper. Sandstorm is fleet density infra: checkpoint-restore lifecycle, multi-node placement, and warm restores measured in tens to hundreds of milliseconds so agent code can sleep cheap and wake on demand.

Capabilities

API
  • API / SDK surface

Similar tools

agent-infrastructuresandboxgvisorfirecrackerrustself-hosted
Source ↗

Via github

X