What Magenta does today, in the order operators work. The demonstrations use sample data; the capabilities behind them run in early access.
MAGENTA / OPERATOR CONSOLEHow Magenta works · sample data
YOUR SERVER / 04 DEVICES · OUTBOUND ONLY
Control planeSelf-hosted
DEVICE DETAIL
finance-02
Heartbeat 24 s ago
CPU busy42%
Memory in use67%
Disk latency6 ms
StateActive
Every device sends a heartbeat every 30 s and connects outward to your server; a device that goes quiet is marked offline on its own.
OBSERVE UNDERSTAND OPERATEHow Magenta works · sample data, not a live fleet
01
Observe the endpoint.
Cadence reports health every minute and reads what Windows exposes about the hardware: thermal headroom and throttling, disk latency and SMART wear, battery wear and Wi-Fi signal, plus hardware errors, crashes and unexpected shutdowns, explained in plain language. Outages show as gaps, never as zeros.
02
Understand what matters.
Security events from Wazuh and hardware events become signals; serious ones open alerts in an attention queue with an owner and a status. Ask Magenta answers questions about the fleet in plain language. It is read-only, and uses the model your organisation chooses, including one you host.
03
Act, with a record.
Operators request actions from a fixed list: restart a service, reboot, collect diagnostics, repair remote access. Sensitive ones need a second person. Connect opens a remote session through your own RustDesk relay once Cadence has checked the machine is ready. Every step lands in the audit log.