Release Notes

Release 5.0 and the current product direction

Version 5.0 is defined by three major capabilities: Residential Egress, Endpoint Identity, and Fingerprint Awareness. Together they make the VM-centric streaming model more explicit, more governable, and easier to operate at fleet scale.

Version 5.0 highlights

Residential Egress

Operators can define direct, split, and full egress policies backed by a WireGuard exit. This gives Beagle explicit routing control for sensitive targets and policy-driven connectivity.

Endpoint Identity

Hostname, timezone, locale, keymap, and a persistent browser profile are managed per endpoint. This lets the runtime environment reflect the policy and assignment state instead of behaving like an anonymous generic image.

Fingerprint Awareness

The control plane evaluates VM configurations for server and virtio characteristics as risk hints. This makes the architecture more transparent without changing the single-product-path design.

Project trajectory

Early milestones

The project established the Proxmox-native control plane, the endpoint OS boot path, and the Sunshine -> Moonlight operating model.

Control maturity

USB control, endpoint reporting, per-VM artifacts, and UI integration made the host layer operationally coherent.

Version 5.0

Residential Egress, Endpoint Identity, and Fingerprint Awareness turned Beagle into a more governable fleet platform while staying within the single-product-path architecture.

Full history

For the complete change history, read the project changelog on GitHub.

CHANGELOG.md