Browse documentation
Core concepts

Computers are provider-neutral

Ask for the surface and capabilities you need. The router chooses eligible capacity without leaking provider details into your application.

Surfaces

Every computer exposes exactly one primary surface. The contract stays stable even when the selected provider changes.

Browser

Navigation, screenshots, CDP, and live-view handoff.

Computer

A graphical desktop plus command execution and takeover.

Sandbox

Isolated command execution for builds, code, and data work.

Routing policy

A request can specify provider order, exclusions, region, trust, required features, resource minimums, and a maximum hourly price. auto asks the router to choose from all eligible capacity.

JSON
{
  "surface": "sandbox",
  "provider": {
    "sort": "price",
    "allow_fallbacks": true,
    "max_price_per_hour": 0.12
  },
  "minimum_trust": "verified",
  "required_features": ["docker"]
}

Trust and secrets

Trust tiers are ordered community < verified < professional < dedicated. Capacity is not eligible unless it meets the workload's minimum trust. Private secret references require verified-or-higher capacity.

Leases

A caller lease limits computer lifetime independently from the node's internal job lease. Renew an active lease when work continues; expiration releases provider resources even if the caller disappears.