Beagle OS has exactly two layers: the Beagle control plane on Proxmox and the Beagle thin-client operating system on the endpoint. The product path remains fixed: Sunshine in the target VM, Moonlight on the endpoint, managed through Proxmox.
Layer one is the Beagle control plane on Proxmox. It integrates into the Proxmox UI, adds the Create Beagle VM workflow, generates VM-specific artifacts, exposes a local REST API, and manages USB control, egress policy, endpoint identity, and fingerprint awareness.
Layer two is the Beagle thin-client operating system. It is Debian-based, boots directly into Moonlight, and avoids the general-purpose desktop model.
The VM is the streaming target and the provisioning anchor. Beagle generates USB installers and runtime profiles for a specific VM, not for a generic user account that later chooses a target.
Beagle deliberately chooses one protocol, one client, and one server. This reduces operational variance, improves latency-focused testing, and makes endpoint behavior reproducible.
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /beagle/health | Health status of the control plane |
| GET | /beagle/inventory | Fleet and endpoint inventory data |
| GET | /beagle/vm/:id/profile | VM-specific runtime profile |
| POST | /beagle/vm/:id/artifact | Generate a VM-specific artifact |
| GET | /beagle/usb/status | Inspect USB control state |
| POST | /beagle/usb/attach | Attach a USB device to a VM |
| POST | /beagle/usb/detach | Detach a USB device from a VM |
