# Routing and backups

Source: [https://docs.aventail.co.uk/docs/getting-started/routing-and-backups](https://docs.aventail.co.uk/docs/getting-started/routing-and-backups)

Choose where this device sends model requests, then add backup destinations for when an earlier destination cannot answer. Configure the order in **Control**; **Link** receives the settings and prepares any local backup.

This walkthrough uses **Link 2.4.0 on macOS** and personal Control’s **Device routing** page. Install the current Link package for your Control account and keep it running while you apply routing changes.

Requests follow the configured route

A local Link address does not mean local processing. A cloud destination receives the requests routed to it and may charge your provider account. Use approved destinations and harmless test prompts. A local backup needs a compatible model, its engine, enough disk space and enough memory to run it.

## Start with one device

Install Link, sign in and approve the intended computer. In the new setup's **Set up** stage, choose **Use a cloud model**. Link opens that device's routing page in Control. For an existing device, open **Devices**, select it and open **Routing**.

Choose **Set up routing**. The editor has three steps: **First model → Backups → Review**. The example uses an existing Anthropic connection and a local Gemma4 backup; your connections and available models will differ.

### Choose a route and a local backup

Personal Control with Link 2.4.0 · captured 13 November 2026. Editor captures show an existing route opened for editing; model, connection and allowance values are examples.

1.  **Choose the connection and first model**
    
    Choose Cloud provider, a saved connection and an available Cloud model. A new device must be allowed to use the connection. Continue with cloud model.
    
    [Screenshot: Choose the connection and first model. Choose Cloud provider, a saved connection and an available Cloud model. A new device must be allowed to use the connection. Continue with cloud model.](https://docs.aventail.co.uk/img/control/routing-2026-11/routing-first-model.jpg)
    
2.  **Choose a local backup**
    
    Select Add a backup, then This device and a compatible Local backup model. Check memory and disk requirements before Add local backup.
    
    This capture shows Gemma4 already downloaded. A new installation may need the download first.
    
    [Screenshot: Choose a local backup. Select Add a backup, then This device and a compatible Local backup model. Check memory and disk requirements before Add local backup.](https://docs.aventail.co.uk/img/control/routing-2026-11/routing-local-picker.jpg)
    
3.  **Check backup order**
    
    Link tries backups in their displayed order. A backup on this computer is always last. Choose Review routing.
    
    [Screenshot: Check backup order. Link tries backups in their displayed order. A backup on this computer is always last. Choose Review routing.](https://docs.aventail.co.uk/img/control/routing-2026-11/routing-backup-order.jpg)
    
4.  **Review before applying**
    
    Check the first model, backup order and any local download. Select Apply routing. Saving is separate from Link confirming the settings.
    
    [Screenshot: Review before applying. Check the first model, backup order and any local download. Select Apply routing. Saving is separate from Link confirming the settings.](https://docs.aventail.co.uk/img/control/routing-2026-11/routing-review-panel.jpg)
    
5.  **Applied can precede preparation**
    
    Control shows Applied after Link confirms the route, while the local backup may still be downloading. Check both states.
    
    [Screenshot: Applied can precede preparation. Control shows Applied after Link confirms the route, while the local backup may still be downloading. Check both states.](https://docs.aventail.co.uk/img/control/routing-2026-11/routing-applied-panel.jpg)
    
6.  **Wait for the local backup**
    
    Local backup prepared; loads on first request means the backup is prepared without ordinary serving enabled. Test your workflow before relying on recovery.
    
    [Screenshot: Wait for the local backup. Local backup prepared; loads on first request means the backup is prepared without ordinary serving enabled. Test your workflow before relying on recovery.](https://docs.aventail.co.uk/img/control/routing-2026-11/routing-applied-prepared.jpg)
    

**Read how to choose the first destination**

## Choose the first destination

Select **Cloud provider**, **Another device** or **This device**. For a cloud-first setup:

1.  Choose an existing connection from **Connection**. Use **Connect a provider** if your account has no suitable connection.
2.  If Control says the connection has not been allowed on this device, review the intended computer and connection. Select **Allow this device to use this connection**, then **Allow connection**. Saving a provider key and allowing a particular device to use it are separate steps.
3.  Check the connection result. **Test connection** checks the provider connection; it does not prove the whole route or its backups work.
4.  Choose an available **Cloud model**, then **Continue with cloud model**.

The example uses `claude-haiku-4-5-20251001`. Choose a model your provider account can use rather than assuming this exact model is available everywhere. Keep provider keys out of screenshots, shared messages and source control.

**Read how to add a local backup**

## Add a local backup

In **Backups**, choose **Add a backup → This device**. Select a **Local backup model** and choose **Add local backup**.

Control shows the model's download size and the device's reported free memory. Download size is not a memory requirement or a promise that the model will fit. Choose a compatible model that this computer can actually run.

Backups are tried in their displayed order. A backup on **This device** is always last. Use the move controls to reorder eligible backups, or remove a backup from the draft. **No thanks · review** continues without backups when none have been added.

Choose **Review routing**. Check the first destination, backup order and any local download before selecting **Apply routing**.

## Wait for the route and the backup

**Apply routing** saves the configuration. It takes effect after Link confirms that version. An offline device waits until it reconnects; a saved choice is not proof that Link is using it.

Control shows **Applied** after Link confirms the route. Check **Local backup** separately: the model may still be downloading. During first setup, Link shows **Getting your backup ready** and download progress.

Link prepares the local backup without requiring you to turn on ordinary serving for it. The backup loads on its first request. Preparation, loading and a successful response are different states.

In Link, open **Routing** to see the applied primary and backup order. **Manage in Control** opens the editor; routing changes are made in Control. The captured interface also explains that cloud destinations are skipped when offline. A prepared backup still needs sufficient resources to load and answer.

### Check routing in Link

Aventail Link 2.4.1 on macOS · captured 14 November 2026. Account/device identity obscured. Model names and memory values are examples.

1.  **Inspect the applied route**
    
    Routing shows the primary destination followed by the final local backup. Check Applied on this device; Manage in Control opens the editor. A displayed order does not prove failover has been tested.
    
    [Screenshot: Inspect the applied route. Routing shows the primary destination followed by the final local backup. Check Applied on this device; Manage in Control opens the editor. A displayed order does not prove failover has been tested.](https://docs.aventail.co.uk/img/link/routing-2026-11/link-routing.png)
    

The native window above was captured in Link 2.4.1 on 14 November. Its primary model differs from the 13 November Control setup example; both illustrate a cloud primary with a final local backup.

**Read the route checks and recovery steps**

## Check the result

1.  Confirm the intended device is online and Control shows **Applied**.
2.  Check the saved order matches what you chose. Confirm the local backup has finished preparing.
3.  Send a short, non-sensitive request through your connected app or the Link API.
4.  Inspect Link's routing state and Control's **Requests** records to identify where the request ran. A completed response or model label alone does not establish the destination.
5.  Test recovery in a controlled workflow before relying on a fallback for important work. A successful first-destination request does not test failover.

Do not remove a working provider key, interrupt other users' requests or disconnect a shared network just to test a backup. Keep any failure test scoped to the test device and restore its working route afterwards.

## Change the order later

Return to the device's **Routing** page and choose **Edit routing**. The editor shows the current first model and offers **Keep this first model**. Review and apply your changes, then wait for confirmation from Link again.

**Close · keep draft** retains the editor draft. **Discard draft** abandons those edits; it does not remove the applied route. **Remove routing** is a separate control, so check its consequences before using it.

| What you see | What to check |
| --- | --- |
| Connection not allowed on this device | Grant the intended device access to the selected connection. |
| Connection test fails | Check the provider connection and access before applying a route. |
| No suitable cloud model | Refresh the connection's available models and check provider access. |
| Device offline or configuration not confirmed | Keep Link running in the same Control environment and wait for its report. |
| Applied, but backup still downloading | Wait for the separate local preparation status. Applied describes the route configuration. |
| Local model cannot load | Check the model's error, runtime compatibility and available memory. Download size alone does not establish fit. |
| Response used an unexpected destination | Inspect the saved order, applied state and request records. Check whether an earlier destination failed. |

## Using another device

**Another device** selects an eligible computer as a destination. The source computer's **Share with your other devices** setting controls whether its served models can be used by your other computers.

The current interface warns that prompts and replies travel over **unencrypted HTTP on the local network** when using this sharing feature. Use a trusted private network and review access before enabling it. Sharing is unnecessary for the cloud-first, same-computer backup example above.

Organisation administration has a separate [Enterprise routing guide](https://docs.aventail.co.uk/docs/fleet/routing). Its earlier rule editor is not the personal three-step flow described here.
