# Features — Sandbox Router

**Route the workload. Govern every step.**

The right provider, the right account, and your policies from creation to every outbound request.

[Get started](https://console.sandboxrouter.io/) · [Explore the routing model](https://sandboxrouter.io/docs/routing)

## The best fit for every workload

Optimize for the lowest cost, fastest startup, or highest creation success. Keep region, isolation and capabilities as firm requirements.

- **Choose what matters most.** Combine cost, startup latency and reliability in your preferred order.
- **Control where it runs.** Target a region, provider or pool. Add isolation, compliance and network requirements.
- **Place workloads together or apart.** Use affinity and spreading to keep related work close or distribute it across providers.

The interactive example lets you change region and ranking priorities. Its fictional pools illustrate filtering before ranking; they are not provider benchmarks.

[How routing works](https://sandboxrouter.io/docs/routing#requirements-and-preferences)

## Your accounts. Working together.

Use several accounts on one provider, combine providers, or do both. Route across their capacity while keeping credentials and policies separate.

Each pool connects a provider account to the resources it offers. Choose an explicit order, rank matching pools by your priorities, or pin a destination.

Example routes: E2B account A then E2B account B; E2B account A then Daytona account C; or all three in order. Every pool must satisfy the request's requirements. Separate credentials and controls, one sandbox ID.

[Understand accounts and pools](https://sandboxrouter.io/docs/routing#providers-accounts-and-pools)

## Keep creation moving

Capacity limits, rate limits and provider outages can interrupt a start. When a pool cannot serve the request, Sandbox Router tries the next eligible one.

1. **Match.** Find pools that satisfy your requirements.
2. **Rank.** Order them by your routing priorities.
3. **Try.** Check policy and attempt creation, moving on when a pool cannot serve it.
4. **Run.** Keep the first successful placement under the same sandbox ID.

One sandbox ID. Fresh policy checks. Your requirements stay in force.

[Inside creation failover](https://sandboxrouter.io/docs/routing#creation-failover)

## Your rules, throughout the run

Control who can create, where workloads can run, what they can do, and which services they can reach.

| Policy layer | What it controls |
| --- | --- |
| Creation | Decide who can create a sandbox and which resources it can use |
| Lifecycle | Control start, stop, update, snapshot and delete permissions independently |
| Provider and account | Apply rules to specific provider pools and account boundaries |
| Individual actions | Authorize commands, file access, port access and credential use |
| Egress proxy | Control outbound destinations and the credentials attached to matching requests |

Policies work together across layers, including during failover. A denied action stays denied.

[Explore policy layers](https://sandboxrouter.io/docs/routing#policy-at-every-layer)

## Connect your APIs. Protect your keys.

Control outbound destinations and add credentials at egress, outside the sandbox. Each matching request uses only the connections it is authorized to use.

Network enforcement and credential injection follow the selected provider's capabilities.

The request flows from sandbox to egress proxy to destination API. The proxy checks policy and adds the credential. The real credential stays outside the sandbox.

[How egress policies work](https://sandboxrouter.io/docs/routing#egress-and-credential-policies)

## One interface. The whole lifecycle.

- **Commands and files.** Run commands, stream output and move files through one API. [Execution](https://sandboxrouter.io/docs/sandboxes#run-commands)
- **Images and snapshots.** Start from an image or restore saved state using the provider's supported formats. [Snapshots](https://sandboxrouter.io/docs/sandboxes#snapshots)
- **Lifecycle controls.** Start, stop and delete sandboxes. Stop idle compute automatically. [Lifecycle](https://sandboxrouter.io/docs/sandboxes#start-stop-and-restart)
- **Usage and audit.** Track activity, resource usage and the actor behind lifecycle changes. [Usage](https://sandboxrouter.io/docs/billing)

## Put your providers to work

One integration. Your accounts. Your rules.

[Get started](https://console.sandboxrouter.io/) · [Read the guide](https://sandboxrouter.io/docs/routing)