Sandboxes
A computer for every run. Sealed by default.
Each run gets a machine of its own, with the internet off until you allow it.

RunStarted by Maya
Clean the March export
- Internet
- Private ranges
- Cloud metadata
- Secret environment variables
This run is audited
Room to work. No way out.
Agents run what they need, where nothing else can be reached.
Its own computer.
A separate machine for each run, owned by whoever started it.
Internet off by default.
Egress policy per org, workspace and environment.
It can't let itself out.
Agents cannot widen their own network.
The details.
- Private ranges blockedYour internal network stays out of reach.
- Cloud metadata blockedNo path to the host's credentials.
- No secrets in the environmentSecret environment variables are refused.
- Kill switchesStop any run.
- E2B-compatible APICode written for E2B runs here.
Where Sandboxes sits.
One stack, from the agent to the ground it runs on.
For peopleOrbit
ControlTitanIdentityPolicyApprovalsLedgerKill switchBuilt with the SDKYour agents
AppsConnectionsKnowledgeAtlasMemoryMemoryModelsRouter
ComputeSandboxes
Long runsHarnessSchedulesRoutinesKnow-howSkillsThe webWaypointYour groundCloud · Edge · On-prem · Air-gapped
Sign-inIdentityRuns where you run.
From the public cloud to networks sealed from the world.
01CloudLive in minutes.
02EdgeBeside the work.
03On-premYour servers. Your walls.
04Air-gappedNothing gets out.
- Internet off by default
- Cloud metadata blocked
- Every run audited
- Kill switches
Questions.
Is a sandbox online?
Not until you allow it. Egress policy is set per org, workspace and environment.
Can an agent change its own network access?
No. Agents cannot widen their own network.
What is blocked?
Private address ranges and cloud metadata endpoints. Secret environment variables are refused, and every run is audited.
Does it work with code written for E2B?
Yes. The API is E2B-compatible.



