Fleet visibility
See node health, host metrics, containers, storage, alerts, and history across client groups.
42 O’Clock Control
The control plane for infrastructure under your care.
Connect remote Linux systems through outbound agents, turn telemetry into accountable action, and keep deployment ownership where it belongs.
What it covers
From first signal to verified recovery.
Control brings monitoring, notification, access policy, and disaster-recovery evidence into one operating surface.
Useful alerting
Route firing and resolved events through scoped channels with throttling and flap suppression.
Infrastructure Vault
Encrypt configuration at the edge before transport so the hub stores ciphertext it cannot read.
Governed actions
Use allowlists, idempotency, audit records, and optional two-owner approval for remote operations.
Flexible headends
Run a lightweight SQLite headend, an ARM64 Raspberry Pi, or a PostgreSQL and Redis cloud topology.
Open-core foundation
Start with the community edition and add licensed MSP capabilities without replacing the agent.
Remote
Static Linux agents support x86-64, 32-bit x86, ARM64, ARMv7, and ARMv6 systems.
Contained
Agent connections are outbound-only, and high-risk functions stay behind explicit feature and policy gates.
Recoverable
Backups, integrity manifests, and restore drills are designed into the operating model.
Next step
Build a disposable Control environment.
The repository includes a full-stack acceptance environment and a ready-to-run test brief.