Agent Sandboxes

Define the computer.
Bound the work.

Place code, browser, and desktop tools inside an explicit execution, state, and network boundary. Isolation is already built, and the task boundary stays explicit.

Who it is for

Agents that must use tools without inheriting the application environment.

The sandbox makes the computer, state, lifecycle, and network reach visible around each task.

Execution stays isolated State has an owner Network reach is defined
  • Agent productsRunning generated codeExecution happens inside a declared boundary instead of the environment that serves your users.
  • Automation teamsDriving browsers and desktopsLong-running sessions keep their state, and outbound access is declared rather than assumed.
  • Security reviewersApproving what an agent may reachNetwork policy, retention and lifecycle are written down before the environment is opened.

What the account receives

A complete boundary for tool-using work.

Tool runtime

Give code, browser, or desktop work a dedicated environment.

The host that serves your users is never exposed to the task.

State boundary

Define what persists and which work owns it.

State stays inside the task that owns it.

Network policy

Set the network reach required by the accepted task.

Outbound access stops at what the work needs.

Lifecycle control

Create, pause, resume, snapshot, and terminate environments deliberately.

The environment starts, pauses, and ends with the task.

Create Run Pause Resume Snapshot Terminate

Ready to give your agents a defined computer?

Tell us what the agents run and where they need to reach. A member of the team replies within one business day.

Request access