# How it works

An animated walk through Sandbox Router: how each request is routed, the three signals behind every routing decision, bursting past one account's rate limit, failover, and one console for every provider.

## Positioning

### One API. Every sandbox.

The routing layer between your workloads and every sandbox provider: demand on one side, supply on the other.

## Routing

### Every request says what it needs.

This one asks for the fastest start, so it goes to the pool that starts quickest.

This one asks for the lowest price, so it goes to the cheapest pool that fits.

This one names a provider, so it goes to exactly that provider.

## Decisions

### Three signals, in order.

Your preferences first, then live analytics, then benchmarks. Every pool left over is a fallback.

### Preferences: your rules.

Requirements filter the pools and your order ranks the rest. A preference never relaxes a requirement.

### Analytics: what's true right now.

Measured on every create: the most reliable pools first, and the most headroom among equals.

### Benchmarks: what the hardware does.

When the machine itself matters: the fastest disk, CPU or network.

### Preferences, then analytics, then benchmarks.

Each layer decides only what the layer above it left open.

## Burst

### Routing is only the start.

Sitting between every workload and every provider, Sandbox Router can do what no single provider can.

### Burst past any one rate limit.

A burst of 1,000 sandboxes in a minute. One account allows 100.

Sandbox Router spreads it across your accounts on the same provider…

…and across providers. Every request is placed, and none comes back 429.

### Pools your rate limits.

Every account and every provider brings its own rate limit, and Sandbox Router adds them up.

### 500 sandboxes, all running.

Our best run so far, replayed in real time: 400 on Freestyle and 100 on Daytona, each create timed from its request to a running sandbox.

## Failover

### When a provider fails, your run doesn't.

Provider A, first in your order, starts returning errors.

Sandbox Router walks your order: Provider A is skipped and Provider B is next, under the same sandbox ID.

New sandboxes land on Provider B. Nothing changes in your code.

## Management

### Every provider, one console.

Accounts, keys, routing, usage, spend and audit, in one place.