What PegaProx adds over the Proxmox VE 9 GUI

Key takeaways

• PegaProx^[1] 0.9.10.2 (released 13 May 2026, 36 versions published, 1.2k stars on GitHub) is an AGPL-3.0 web control panel for managing multiple Proxmox VE 8/9 and XCP-ng clusters from a single screen.
• What the stock Proxmox VE 9 GUI already does is underrated. Before adding layers, get clear on what the native one already covers.
• PegaProx adds three things the stock GUI does not have out of the box: live migration across separate clusters, OIDC with Entra ID and 2FA TOTP, and a CVE scanner plus one-click hardening.
• The intelligent balancing comes from ProxLB^[2] (author: gyptazy), incorporated as a community contribution. Fair to name it.
• Not a single-node tool. If you have one Proxmox in a homelab, the native GUI is enough. PegaProx starts to make sense from two clusters upward, or when VMware/XCP-ng enters the mix.

What the Proxmox VE 9 GUI already does

First, the baseline. The interface that ships with Proxmox VE 9^[3] out of the box is more capable than someone who last saw it on 6.x would remember:

• Datacenter view with aggregated CPU, RAM, storage and HA status per cluster.
• HA and replication configurable from the UI, with groups and fencing policies.
• Ceph integrated (pools, OSDs, monitors) and ZFS from the UI itself.
• Backup and restore via Proxmox Backup Server, with per-job retention and periodic verification.
• SDN (Software Defined Networking) with zones, VNets and subnets that cover most enterprise network patterns.
• ESXi importer since 8.2 to move VMware machines without going through an intermediate OVF.
• Mobile UI functional enough to shut something down from the car.

Where it falls short: one cluster, one session. Native authentication covers PAM, LDAP/Active Directory and 2FA TOTP, but modern OIDC (Entra ID, Keycloak with OIDC flows) only appears via community plugins. And inter-node balancing within a cluster is manual unless you install ProxLB separately.

What PegaProx adds

PegaProx sits one layer above the individual cluster. Its real differentiators on today’s release line:

• Multi-cluster pane. You see every Proxmox in the organisation (plus XCP-ng, in tech preview) from a single URL, with live metrics over SSE.
• Live migration across separate clusters. Native Proxmox allows live migration within the same cluster. PegaProx extends it across separate clusters, which opens evacuation work, scheduled hardware maintenance, and consolidation without service downtime.
• OIDC and Entra ID natively, on top of traditional LDAP/AD. Integrated 2FA TOTP and custom roles above the Proxmox privileges schema.
• Intelligent balancing based on ProxLB, gyptazy’s project already known in the community. PegaProx ships it as the automatic balancing engine, redistributing load by CPU, RAM and usage patterns.
• Integrated CVE scanner that crosses installed packages against public vulnerability feeds and flags affected nodes.
• One-click PVE hardening, replicating practices that usually go in by hand (SSH config, sysctl, journald, fail2ban, kernel parameters).
• ESXi and XCP-ng bridge to import and migrate machines from VMware and Xen without building the pipeline by hand.

Live migration between separate clusters in PegaProx. It is the most visible difference vs the stock Proxmox VE 9 GUI, which only supports live migration within the same cluster. Screenshot from the official PegaProx site.

User and RBAC management in PegaProx, with OIDC and Entra ID on top of the native Proxmox privileges schema. Screenshot from the official PegaProx site.

Comparison table

When it fits and when it doesn’t

Fits well when:

• You operate two or more Proxmox clusters and the friction of jumping between URLs and audit dialects starts to cost real time.
• Your organisation requires OIDC with Entra ID or Keycloak, and community plugins for Proxmox feel too fragile for production.
• You’re migrating from VMware or XCP-ng and prefer a web tool to a hand-rolled qm importovf and xe vm-export pipeline.
• You want automatic inter-node balancing without installing ProxLB separately and maintaining its config on the side.

Does not fit when:

• You run a single Proxmox or a small cluster and the stock GUI covers your needs. Adding another layer is net complexity with no payoff. For a small homelab, a Docker-based PaaS like Coolify tends to cover what you need without touching the hypervisor panel.
• You plan to redistribute PegaProx inside a closed product, embed its code, or build a SaaS on top without releasing derivatives. AGPL-3.0 is contagious.
• You need a support contract with SLA and legal backing. PegaProx does not offer one. Proxmox does, via subscription.

Honest risks

The project is real and moving. v0.9.10.2 dropped on 13 May 2026, there are 36 releases, 274 commits, 1.2k stars. A few things to keep in mind before putting it on critical infrastructure:

• Pre-1.0. 33 open issues and 4 PRs in queue. The team is three people (Nico Schmidt, Marcus Kellermann, Laura Weber) under the SocialFurr organisation. Active, not mature.
• No affiliation with Proxmox Server Solutions GmbH. The authors say so explicitly. It’s not an official tool and there’s no joint roadmap with upstream.
• AGPL-3.0. If you plan to integrate it in a product you distribute to third parties or expose as SaaS, AGPL requires you to release derived code. It’s a legal decision more than a technical one.
• Marketing aiming high. The site mentions use in Healthcare, Finance, Defense, Government, Law Enforcement. No public way to verify names or volumes. A claim, not a fact.

Quick install

Three ways, all documented in the repository:

1. Deploy script:

   Copy

   curl -sSL https://raw.githubusercontent.com/PegaProx/project-pegaprox/refs/heads/main/deploy.sh | sudo bash

2. Debian 13 LXC template prebuilt, importable directly into a Proxmox cluster.

3. Debian VM image prebuilt if you prefer isolating PegaProx in its own virtual machine.

Requirements from the README: Python 3.8 or higher, Proxmox VE 8.0+ or 9.0+, XCP-ng 8.2+ if you want the bridge, modern browser. For those who’d rather not pipe sudo bash directly, the repository has deploy.sh readable and docker-compose.yml available to audit first.

Verdict

PegaProx delivers on the multi-cluster claim, and its ProxLB integration is honest. For infrastructure with two or more clusters, corporate OIDC and a need to migrate from VMware, installing it in pre-production and letting it run for a few weeks is a cheap test. For a single-node homelab or a small cluster where the stock GUI covers everything, no need. Before putting it in critical production, wait for 1.0 or accept the risk of a pre-release that moves every week. If what you want is lighter virtualisation for multi-tenant services, Firecracker microVMs is another path with different tradeoffs.

Frequently asked questions

What is PegaProx? PegaProx is an open-source web control panel under the AGPL-3.0 licence for managing multiple Proxmox VE 8/9 and XCP-ng clusters from a single interface. It is maintained by a three-person team under the SocialFurr organisation and is not affiliated with Proxmox Server Solutions GmbH.

Is PegaProx free? Yes. PegaProx is 100% free under the AGPL-3.0 licence, with no paid tiers and no registration required. The project is sustained by voluntary sponsors, and all features are available to every user.

Does PegaProx work with Proxmox VE 9? Yes. According to the official README, PegaProx supports Proxmox VE 8.0+ and 9.0+, plus XCP-ng 8.2+. It requires Python 3.8 or higher and a modern browser.

How does PegaProx differ from the Proxmox VE 9 GUI? The stock Proxmox VE 9 GUI manages one cluster at a time. PegaProx adds multi-cluster view, live migration across separate clusters, OIDC authentication with Entra ID, an integrated CVE scanner, one-click hardening, and a bridge to VMware ESXi and XCP-ng.

Is PegaProx production-ready? PegaProx sits at v0.9.10.2 (pre-1.0). As of 14 May 2026 it has 36 releases, 274 commits, and 1.2k stars on GitHub, but it has not yet reached a stable 1.0. For critical infrastructure, wait for the 1.0 milestone or accept the risk of an actively-moving pre-release.

Data verified on 14 May 2026 against the official PegaProx repository and the Proxmox VE documentation.

1. PegaProx
2. ProxLB
3. Proxmox VE 9