Gather
- →Pull specs and sources
- →Stage work for the next agent
Every agent runs isolated. The whole fleet shares one workspace — handoffs are instant, glue code is gone.
Create an account and spin up your first multi-agent sandbox — isolated agents, one shared workspace.
Factory
Build, test, and ship with agents that pass work cleanly — each step isolated, everything shared where it should be.
Reproduce, patch, and test — each agent in its own sandbox, review packs ready for the next teammate.
Scout agents fan out in parallel; a synthesizer pulls everything together from the same workspace.
Coordinate whole fleets — each agent isolated, the whole group collaborating in one workspace.
Launch agent A, leave work for agent B, keep going. Stop the agents — the work remains. That’s the multi-agent sandbox.
Isolate
Every agent runs in its own sandbox. Risky work stays contained — your host and other agents stay protected.
Each agent gets a private sandbox — not a shared container soup.
Untrusted output stays inside the sandbox boundary.
Agents don’t wander the open internet by default.
Keep fleets from runaway spend and runaway scale.
Each agent gets a private sandbox — not a shared container soup.
Untrusted output stays inside the sandbox boundary.
Agents don’t wander the open internet by default.
Keep fleets from runaway spend and runaway scale.
The reason multi-agent systems finally work: one durable workspace every agent can read and write.
Agent A writes. Agent B reads. No custom glue.
Stop an agent — the files remain for the next one.
Many agents write at once without stepping on each other.
Handoffs measured so you know agents stay in sync.
Agent A writes. Agent B reads. No custom glue.
Stop an agent — the files remain for the next one.
Many agents write at once without stepping on each other.
Handoffs measured so you know agents stay in sync.
Lifecycle latency that keeps fleets moving — create, wake, and first exec measured against a live peer sandbox.
Peer sandbox ~1293 ms — about 2.2× faster on the same clock.
Standby wake — back in without a cold create.
Peer sandbox ~416 ms on the product path.
Room fill green — create 503 rate 0 under load.
Peer sandbox ~1293 ms — about 2.2× faster on the same clock.
Standby wake — back in without a cold create.
Peer sandbox ~416 ms on the product path.
Room fill green — create 503 rate 0 under load.
Stand up rooms, launch agents, and watch the trail — from your stack or from agent tools.
Create rooms, launch agents, run work, read results.
Your agents can operate the sandbox themselves.
See launches, handoffs, and finishes across the fleet.
Create, resume, and first exec measured on the landing.
Create rooms, launch agents, run work, read results.
Your agents can operate the sandbox themselves.
See launches, handoffs, and finishes across the fleet.
Create, resume, and first exec measured on the landing.
Create, resume, and first exec — p50 on public HTTPS vs a live peer sandbox (measured side-by-side).
Create
~594 ms
~2.2× faster
Resume
~4 ms
Standby wake
First exec
~253 ms
~1.6× faster
Lifecycle that matches how fleets actually run — wake fast, fill a room, leave work behind.
Resume
~4 ms
Standby wake — start again without a cold create.
Room fill
16 agents
One room filled via from-template · create 503 rate 0.
Stop
Work stays
Stop the agents — Drive keeps the files for the next one.
Concurrent
16
Free and Starter soft cap — same concurrent sandbox budget.
Not a single-agent playground — fleets that collaborate safely, with handoffs you can trust.