# isolance — One API. Every sandbox.

Run workloads across sandbox providers through a single integration. Optimize for cost, performance, and availability—without vendor lock-in.

Get started in the [console](https://console.isolance.com/), or read the [docs](https://caas.sh/docs).

The website shows this routing preview: runs are triggered from GitHub, Linear, webhooks or the API and CLI. Provider X is at capacity, so isolance fails over to E2B, with Freestyle also shown as a routing option:

```text
$ iso run --from . -- npm test
  placed on Provider X
  capacity → failed over to E2B
✓ running on E2B
```

## One layer between your agents and every provider

### Route — one API over every provider

Start sandboxes and VMs through one API, CLI and console. Auto places each run by capacity and price.

- **Your provider keys.** Pay providers directly, at their prices.
- **Auto placement.** By capacity and price, with failover.
- **One interface.** The same API, CLI and console for every provider.

### Run — agents, ready to go

Run Claude Code or Codex in your own image, with connectors whose keys never enter the sandbox.

- **Your own image.** Claude Code or Codex, set up your way.
- **Connectors.** Keys are added at egress, never inside the sandbox.

## Providers

Daytona, E2B, Freestyle, Maritime. Your keys, your provider bill.

## Route your first run

One API for every sandbox, and every event delivered. Get started in the [console](https://console.isolance.com/).

## Explore

- [Features](https://caas.sh/features.html)
- [Pricing](https://caas.sh/pricing.html)
- [Docs](https://caas.sh/docs)