Menu ☰
Tiller Router

Automatic fallback when an AI model fails.

Get from GitHub

Set a preferred model and backups so a provider outage doesn't have to stop your next request.

Tiller Router routing diagram showing client requests passing through virtual models to primary and fallback providers

Choose the fallback order

A virtual model in Tiller Router can point to several real models. Your application requests the same virtual model every time. Tiller tries the preferred provider first and can move to a backup when a supported error occurs.

For example, you might use a low-cost model normally, with a second provider available when it is rate-limited.

Tiller Router ordered fallback configuration screen showing a virtual model with several backup targets and routing order controls

When a provider fails

Fallback occurs transparently to clients within Tiller Router. The replacement model handles the turn and the failed one is skipped for a definable cooldown period.