# Architecture and data flow

Source: [https://docs.aventail.co.uk/docs/introduction/platform-architecture](https://docs.aventail.co.uk/docs/introduction/platform-architecture)

See how Control, Link, Workspace and your applications communicate.

### Follow the two data paths

Process overview; detailed actions and examples are below.

1.  **Follow the two data paths**
    
    Control manages devices; applications send inference requests to a serving endpoint.
    
    -   Control → hosted services: Registration and management
    -   Hosted services ↔ Link: Commands and status reports
    -   Application ↔ local model: Inference requests and responses

**Read the architecture and data-flow details**

## Products

| Product | Responsibility |
| --- | --- |
| **Control** | Browser interface for accounts, devices, models, deployments and operational records |
| **Aventail Link (Link)** | Installed runtime that receives management commands and runs models on a device; version 1.x is documented as Locai Link (Legacy Aventail) |
| **Workspace** | Chat and document interface; can use a Link node or a separate browser model |
| **Fleet** | Organisation controls for groups of devices and configuration rollouts |

## Management path

```mermaid
flowchart TD
  A["Control in your browser"] --> B["Hosted management services"]
  B -->|Deploy / configure| C["Link on your device"]
  C -->|Status reports| B
```

Registration, downloads and hosted Control require connectivity. An installed model and its running inference endpoint are separate from the availability of the hosted applications.

## Inference path

```mermaid
flowchart TD
  A["Workspace or your application"] -->|Request to a serving endpoint| B["Link on your device"]
  B --> C["Local model"]
  C -->|Response| A
```

The first walkthrough used Workspace and an API client on the same Mac as Link. Other-machine access depends on the serving address, port and network configuration.

**This device** in Workspace is a separate WebGPU path: the model runs in the browser rather than in Link.

### Device reports

Control can show device identity and version, resource measurements, operation logs, deployment progress and inference records. The tested language-model request appeared as **stats\_only**. Do not assume that every pipeline reports the same fields.

### Management commands

Deployment and start/stop actions are sent to Link. Keep the device online and confirm the resulting state rather than treating command submission as completion.

### Updates in Control

Device and operation views update as reports arrive. Check the last-seen time when diagnosing stale state; reporting intervals depend on configuration.

## Security and privacy

Local execution does not make every connection local or encrypted. Review the [serving endpoint](https://docs.aventail.co.uk/docs/getting-started/initial-setup#serve-a-model) separately from hosted account access.

### Data handling

Check the application's storage, analytics and reporting settings as well as Link's configuration. See [privacy controls](https://docs.aventail.co.uk/docs/privacy/usage-analytics) and [security and access](https://docs.aventail.co.uk/docs/guides/security). Certification, transport guarantees and offline deployment requirements need deployment-specific evidence.