// the take
PegaProx is a self-hosted web dashboard for managing one or more Proxmox VE clusters (plus a tech-preview XCP-ng integration) — VM/container lifecycle, live migration, HA, backups, and reporting, built in Python/Flask with a React-ish frontend. It's aimed at sysadmins running Proxmox past the point where the stock web UI is enough, especially across multiple clusters or while migrating off ESXi.
The dedicated transfer network for cross-cluster migration and replication traffic, kept off the management network, is a concrete design decision rather than a bullet point. Direct ESXi-to-Proxmox migration (pyvmomi/SSHFS, with VirtIO driver pre-staging for Windows guests) solves a real problem for anyone leaving VMware right now. The DB encryption key custody chain — env var, then systemd TPM2-bound credential, then a permission-checked key file that's refused outright if its mode is too loose — is more careful than most self-hosted tools bother with.
Three people maintaining this much surface — multi-cluster HA with majority-vote automatic failover, LDAP/OIDC/WebAuthn, a SIEM forwarder, Ceph management, cost/carbon accounting, and cross-hypervisor migration — is a lot to keep correctly tested, and the less-trodden paths are where that will show. The test suite has a long run of files named after specific automated-scanner findings (test_aikido_*, batch-numbered by date), which signals a meaningful chunk of the hardening here is reactive patching after a scanner flagged something rather than designed in up front — worth reading the actual diffs before trusting this with cluster credentials. The compliance dashboard maps to ISO 27001/SOC2/HIPAA/NIS2, but the backup-verification feature it partly leans on is explicitly marked experimental, so treat the mapping as a checklist, not an audit. Automatic HA failover for the management plane itself (quorum vote, optional witness) is marked beta, and that's exactly the kind of feature that needs a long real-world track record before it's making unattended failover calls.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →