Governor Server Management
A Windows desktop console for operators. One place to see every client workspace, every project and server, what needs approval, what has been backed up and what the Memory archive holds. It is in active use across multiple internal and external pilots, in advisory mode.
THE PRODUCT, EXPLAINED
Keep your business moving.
Start with the short film. Then see how it works in the full demonstration.
One connected view of your systems, their warning signs and your next step.
Press Play. CC adds captions. Use full screen for the clearest view.
Illustrative scenarios. * Extended features in final R&D.
One console for an operator who serves several organizations
Operators who run servers and fleets for more than one organization need to keep each client's systems, records and decisions cleanly apart while still seeing everything from one place. Governor Server Management is that place: a Windows desktop console that gathers the operator's client workspaces, a status wall for projects and servers, the items waiting for approval, the state of backups and the Memory archive.
The console is in active use across multiple internal and external pilots, in advisory mode. It shows the operator the state of the fleet, surfaces what needs a decision and keeps the reviewed knowledge about each client at hand; the operator takes the decisions.
Windows desktop console
Installed on the operator's workstation, with the fleet view, approvals and archive in one application.
Per-client separation
Each client has its own workspace, so organizations never mix on the operator's screen or in the records.
Advisory mode today
The current operating mode in internal use: the console informs and gathers approvals; the operator acts.
The five views
Each view answers one operator question. Together they cover the daily work of running fleets for several clients.
Client workspaces
Each client's fleet, projects and records live in their own workspace, so an operator who serves several organizations keeps them cleanly apart.
Project and server wall
A wall of status lights for projects and servers, fed by monitoring adapters, so the state of a whole fleet is readable at a glance.
Approvals view
Items that need an operator's decision are gathered in one view, so nothing waits unnoticed and every decision is taken deliberately.
Backups
A backups view that shows what has been protected and when, alongside the servers it belongs to.
Memory archive
The console reuses Governor Memory, so the operator's reviewed knowledge about each client, with its provenance, is available where decisions are made. Memory keeps an immutable journal, reviewed knowledge with provenance, exact-text sources and ranked search; projects are isolated by default and shared knowledge is never auto-accepted.
Governor's own stack, plus the monitoring a fleet already runs
The status wall is fed first by Governor's own monitoring stack, and it also reads from the monitoring a fleet already runs rather than replacing it. More sources are being added.
Governor's own stack
- Governor Monitoring Agent: Governor's own endpoint agent, carrying host metrics and endpoint security to the wall
- Governor Monitoring Collector: a first-party collector that normalizes sources
- Governor Server Sentinel: the analysis and response-tier service
- Governor Memory: the client-separated evidence and knowledge store
- Independent watchdog: supervises the monitoring system itself
Adopts what a fleet already runs
Where a fleet already runs them, Server Management reads from existing tooling through its built-in adapters.
- Uptime Kuma: availability and uptime checks
- Prometheus: host and application metrics, including node_exporter host metrics and Alertmanager routing
- Wazuh: endpoint security findings and events
- and existing fleet tooling where deployed, such as CrowdSec, auditd, blackbox_exporter, Gatus and Restic
| Source | What it brings to the wall | Status |
|---|---|---|
| Governor Monitoring Agent | Governor's own endpoint agent: host metrics and endpoint security | Available now |
| Uptime Kuma | Availability and uptime checks | Available now |
| Prometheus | Host and application metrics (node_exporter, Alertmanager) | Available now |
| Wazuh | Endpoint security findings and events | Available now |
| Existing fleet tooling | CrowdSec, auditd, blackbox_exporter, Gatus and Restic, read where already deployed | Adopted where deployed |
| RansomShield agent | Protection and detection telemetry from the RansomShield agents | Coming next |
| Windows host metrics | Host metrics on Windows endpoints | Coming next |
| Grafana | Packaged engineering dashboards | Coming next |
| Suricata, Zeek, Velociraptor | Selectable network-detection and investigation sensors | Coming next |
The operator's safety layer around governed automation
Server Management and Server Sentinel are designed to work alongside Governor AI as the operator's additional safety layer. Governor AI governs the automation; the console shows the operator the state of the fleet it acts on.
Works alongside Governor AI
Governor AI governs the automation; the console shows the operator the state of the fleet it acts on and gathers what needs a decision.
Pairs with Server Sentinel
Sentinel gathers evidence and analyses incidents on the Linux fleet; the console gives the operator the fleet-wide picture and the approvals.
Shares Governor Memory
One reusable Memory component, so knowledge is kept with provenance and independent of any one AI model.
Standalone program
A reusable Governor program with one authoritative source; client-specific configuration and state kept separate.
Bespoke delivery
Delivered as part of a system designed and built for each client, customer-hosted or Governor-managed.
Internal pilot
The console is in active use across multiple internal and external pilots, in advisory mode.
Governor Server Management at a glance
Talk to us about your fleet
Request a briefing on Governor Server Management and the product line around it.
Request a Briefing