PrivateNexus is a self-hosted infrastructure operations platform. It sits above the tools you already run — Proxmox, Caddy, DNS, identity, Docker, monitoring, and backups — and gives you one governed layer across all of them.
It doesn't replace your stack. It answers the questions your stack can't answer on its own: what exists, is it working, can it be recovered, who changed it, and what's safe to do right now.
Self-hosted infrastructure grows through necessity — one service becomes twenty, and it's easy to end up relying on memory and scattered notes. Existing tools each solve part of the puzzle: Proxmox knows about VMs, Docker knows about containers, your monitoring stack knows about metrics. None of them, on their own, can tell you whether a specific service could actually survive an incident, or who's allowed to change it, or whether a backup that ran last night is actually restorable.
PrivateNexus is the instrument panel for that. It doesn't run the engine room for you — but it makes the engine room understandable, recoverable, and governable, from one place.
Three ideas run through everything in PrivateNexus:
New to PrivateNexus? Getting Started walks through your first few minutes — signing in, what to expect on an empty dashboard, and the fastest way to see the platform do something real.
This documentation covers features that are real, built, and verified working — not a roadmap of what's planned. If something you expected isn't here, it's worth checking the FAQ before assuming it's missing by mistake.