Architecture and data flow
See how Control, Link, Workspace and your applications communicate.
Follow the two data paths
View 1 of 1: Follow the two data paths.
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
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
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 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 and security and access. Certification, transport guarantees and offline deployment requirements need deployment-specific evidence.