Every service you register in PrivateNexus gets its own card on the dashboard, grouped by workspace (Infrastructure, Business Systems, Personal Services, Monitoring, or your own custom groupings). Each card shows live status at a glance — no SSH session required.
PrivateNexus probes each registered service on a continuous 2-minute cycle. Two check types are supported:
tcp://host:port)Results are written to a running history, not just the current state — so a status page always reflects genuinely fresh data, not a stale snapshot.
Every service's detail view has a Recovery Score panel: a score and letter grade reflecting how confident PrivateNexus is that the service could actually be restored if it went down today. The score accounts for whether a real backup exists, how recent it is, and whether it's been trust-verified — not just whether a backup job ran.
Each service can have backup records attached directly to it — add a backup, mark it as Last Known Good (LKG), and track its trust state over time. This is what feeds the Recovery Score: a backup job reporting success isn't the same thing as a backup you can actually trust to restore.
Every action taken through PrivateNexus — who did it, what it targeted, and the outcome — is written to an immutable, tenant-scoped audit log. This is the record you'd pull during a postmortem, not something you have to reconstruct from memory.