Control, by construction.
How the pieces fit, and why. For Magenta the trust model is the architecture: devices start every connection, a second person approves what matters, and everything runs on infrastructure you hold.

Cadence
Windows agent · observes, queues locally, acts from an allowlist
Control plane
Backend and database · Wazuh manager · RustDesk relay
Console
Fleet · attention · approvals · audit
From endpoint to operational picture.
Cadence writes each observation to a queue on the device first, then uploads it. Rows leave the queue only after your server confirms them, so an outage delays data rather than losing it. Every request is signed with the device’s own key, and a device is trusted only after an administrator confirms it.
From operator to endpoint.
Your server never connects into a device. Approved actions wait until Cadence collects them on its next poll and runs them from the list compiled into it. Remote sessions travel through your own RustDesk relay, not through Magenta.
Reboot, with a second pair of eyes.
A reboot needs approval from someone other than the person who asked. The device is never pushed a command: Cadence collects approved work outward and runs only actions compiled into it.
- 01Requested, with a reason
- 02Approved by a second operator
- 03Collected by Cadence on its next poll
- 04Performed from the agent’s allowlist
- 05Result reported and recorded