SYSTEM ARCHITECTURE

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.

Endpoint machines linked to self-hosted server hardware
01 / ENDPOINT

Cadence

Windows agent · observes, queues locally, acts from an allowlist

02 / YOUR SERVER

Control plane

Backend and database · Wazuh manager · RustDesk relay

03 / OPERATOR

Console

Fleet · attention · approvals · audit

OBSERVATIONS FLOW IN

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.

ACTIONS ARE COLLECTED, NOT PUSHED

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.

MAGENTA / OPERATOR CONSOLEHow Magenta works · sample data
SENSITIVE ACTION

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.

reboot → finance-02 · reason: pending Windows update
  1. 01
    Requested, with a reason
  2. 02
    Approved by a second operator
  3. 03
    Collected by Cadence on its next poll
  4. 04
    Performed from the agent’s allowlist
  5. 05
    Result reported and recorded
OBSERVE UNDERSTAND OPERATEHow Magenta works · sample data, not a live fleet