The ultimate datacenter management solution for Proxmox VE and XCP-NG. Unified multi-cluster control, intelligent load balancing, and seamless cross-cluster VM migrations — all in one beautiful interface.
Keine Überschriften im README
PegaProx
Modern Multi-Cluster Management for Proxmox VE & XCP-ng
PegaProx is a powerful web-based management interface for Proxmox VE and XCP-ng clusters. Manage multiple clusters from a single dashboard with features like live monitoring, VM management, automated tasks, and more.
The name PegaProx is inspired by Pegasus, the winged horse of Greek mythology, combined with Prox as a reference to Proxmox VE. Pegasus symbolises speed, freedom and elegant flight - qualities we aspire to bring to multi-cluster hypervisor management.
PegaProx is a community-driven open source project that lives entirely from sponsorships and donations. Server costs, domains, code-signing certificates and the developer hours behind every release come straight out of our own pockets — and out of the contributions of the wonderful companies and individuals below. If PegaProx saves you time at work, please consider becoming a sponsor or chipping in on Open Collective. Every euro keeps the lights on. 💛
🖥️ Unified Dashboard - Manage all your Proxmox clusters from one place
📊 Live Metrics - Real-time CPU, RAM, and storage monitoring via SSE
🔄 Live Migration - Migrate VMs between nodes with one click
⚖️ Cross-Cluster Load Balancing - Distribute workloads across clusters
🛣️ Transfer Network - A dedicated network per cluster for the disk data of cross-cluster migrations, replications and Site Recovery runs, off the management network (docs)
🔄 Cross-Hypervisor Migration - Migrate VMs between ESXi, Proxmox VE, and XCP-ng
▶️ Quick Actions - Start, stop, restart VMs and containers
⚙️ VM Configuration - Edit CPU, RAM, disks, network, EFI, Secure Boot & more
📸 Snapshots - Standard and space-efficient LVM snapshots for shared storage
🔁 Snapshot Replication - Storage-agnostic replication for clusters without ZFS
💾 Backups - Schedule and manage backups
✅ Backup Verification(Experimental) - Automated restore → boot → health check → cleanup (ISO 27001, SOC 2, HIPAA compliance)
🖱️ noVNC / xterm.js Console - Browser-based console for QEMU and LXC
⚖️ Load Balancing - Automatic VM distribution across nodes
🔁 High Availability - Restart the guests of a failed node elsewhere, with fencing, a self-fence agent and only guests whose volumes are on shared storage
📍 Affinity Rules - Keep VMs together or apart on hosts (QEMU + LXC)
👥 Multi-User Support - Role-based access control (Admin, Operator, Viewer) + custom roles
🛠️ API Token Management - Create, list, and revoke Bearer tokens (scoped per role)
🔐 2FA Authentication - TOTP-based two-factor authentication (with force option)
🔑 WebAuthn / FIDO2 - Hardware-key login (YubiKey, Nitrokey, Touch ID, Windows Hello) - passwordless or as 2FA factor
🏛️ LDAP / OIDC - Active Directory, OpenLDAP, Entra ID, Keycloak, Google Workspace, Authentik (with PKCE)
🛡️ VM-Level ACLs - Fine-grained permissions per VM
🏢 Multi-Tenancy - Isolate clusters for different customers
🚫 IP Whitelisting / Blacklisting - Restrict access by IP or CIDR range
🔒 Full-DB Encryption - SQLCipher (AES-256-CBC + HMAC-SHA512, format v4) wraps the entire database at rest on Linux x86_64; sensitive fields stay individually Fernet-encrypted everywhere else. Multi-tier master-key loader resolves from env / systemd LoadCredentialEncrypted / /etc/pegaprox/secret.key, so a config/ backup never carries the key alongside the data. Auto-migrates plain DBs on first boot post-update.
🔍 CVE Scanner - Per-node package vulnerability scanning via debsecan
🛡️ CIS Hardening - One-click security audit and hardening against CIS benchmarks
🧾 HMAC-Signed Audit Log - Tamper-evident integrity verification on every entry
📋 Integrated Syslog Server - Receive and view syslog messages (UDP/TCP) with filtering, search, and severity-based coloring
🧬 Config Drift Detection - Nightly snapshot of cluster config (VM configs, storage.cfg, network, datacenter options) - alerts on any unauthorized change vs the admin-set baseline. Pairs with the Compliance Dashboard.
💰 Cost Dashboard / Chargeback - €/VM/Month from real metrics (CPU-h × node tariff + RAM-GB-h + Storage-GB-month). Currency-configurable, per-cluster rates, top-spender table, by-node breakdown. CSV + PDF export.
⚡ Power & Carbon Tracking - Estimated kWh + €/Month + kg CO₂/Month per VM, based on metrics history × node-power profile × PUE × grid CO₂ intensity. Defaults for DE/EU; admin-tunable for any hardware/grid. CSV + PDF export.
🧠 Insights - Right-sizing recommendations (oversized / undersized CPU + RAM, idle VMs) and capacity forecasts (linear regression + ETA to threshold) over 30 days of history. PDF export.
☁️ Cloud-Init Template Library - Curated catalog of the supported Ubuntu LTS, Debian, AlmaLinux, Rocky Linux, Fedora and Alpine cloud images (a weekly CI job checks every image URL and flags releases past their end of life) plus admin-defined custom templates. One-click deploy to any cluster (download → import → cloudinit drive → convert to template).
🚑 Site Recovery - Configure DR plans (boot order, dependencies, replication mappings) and execute controlled failover with audit trail.
📦 Backup SLA Tracking - SLA dashboard per cluster + datastore: last-backup age vs configured RPO, integrated with the Alert pipeline.
🔁 ZFS / Cross-Cluster Replication - Native PVE replication monitor + cross-cluster replication for clusters without shared storage.
🪽 PegaProx High Availability - Pair up to 4 PegaProx instances: standbys keep a copy of the configuration, show a live view and pass changes on to the leader; failover is a confirmed, manual promote, or (beta, switched on per group) automatic by majority vote, with an optional witness as the third vote
🧩 Automated PVE Installations - Serve answer files for the Proxmox VE auto-installer from profiles (guided setup or editor) and follow every installation run
🛠️ V2P / ESXi Migration - Pyvmomi + SSHFS-based, with VirtIO driver pre-staging via MSI bulk-install (Windows guests).
🔔 Web Push Notifications - Browser push via VAPID, “wake-up” pattern (no payload leaks to push provider). Inbox view in the topbar bell with unread badge.
🌐 Client Portal - Self-service portal for hosting customers with VM power actions, noVNC console, snapshots, ISO mount, snapshot policies (read-only), 2FA, and password management
📊 Public Status Page - Cluster health dashboard for monitoring screens with URL-based auth key (no login required)
📱 Responsive + PWA - Works on desktop and mobile, installable as native-feeling app
📦 PBS Integration - Proxmox Backup Server management with backup verification
🔭 Prometheus Exporter - Scrape /api/metrics with a bearer token (an admin's or one with metrics.view) for cluster, node, guest, storage, replication and backup-age metrics
This installation method pulls the deployment script directly from the current HEAD of the main branch. This means you will always receive the latest available version, including the most recent features and improvements. However, because it is not tied to a specific release, it may also contain unreleased changes or bugs that have not yet been fully tested. If you prefer a stable and tested version, consider installing PegaProx from a tagged release instead.
This installation method uses the official APT repository provided by gyptazy. The repository and its associated build and packaging pipeline are fully hosted and maintained by gyptazy, where PegaProx releases are automatically built and published as Debian packages. Unlike the automated installation script, which pulls the latest code directly from the repository branch, the APT repository distributes packaged and versioned releases. This generally provides a more stable and predictable installation, making it the recommended approach for production environments.
curl https://git.gyptazy.com/api/packages/gyptazy/debian/repository.key -o /etc/apt/keyrings/gyptazy.asc
echo"deb [signed-by=/etc/apt/keyrings/gyptazy.asc] https://packages.gyptazy.com/api/packages/gyptazy/debian trixie main"| sudo tee -a /etc/apt/sources.list.d/gyptazy.list
apt-get update
apt-get -y install pegaprox
This installation methods run PegaProx directly from the source code repository. It is primarily intended for development, testing, or advanced users who want full control over the codebase or want to modify and extend the project.
By default, cloning the repository will pull the latest state of the main branch, which contains the most recent changes and features. While this ensures you always have the newest code available, it may also include in-progress changes that are not part of an official release yet.
If you prefer a more stable version, you can optionally checkout a specific release tag from the repository before installing dependencies and starting the application. This allows you to run the exact code corresponding to an official release while still using the source-based installation method.
Running PegaProx from source can be useful for debugging, contributing to the project, or integrating custom functionality, since you have direct access to the entire codebase and can easily update it using standard Git workflows.
The same image is on Docker Hub as pegaprox/pegaprox, with the identical digest, so pegaprox/pegaprox:latest works just as well. Other PegaProx images on Docker Hub are not ours and may be outdated.
From 1.4.1 on, the Docker images and the VM/LXC appliance images carry a signed build provenance attestation, so you can check that an image was built by our release workflow from this repository:
Database at rest → SQLCipher (AES-256-CBC + HMAC-SHA512, SQLCipher format v4) on Linux x86_64. Plain SQLite + per-field Fernet on other platforms (ARM / macOS / Windows). See docs/SECURITY.md for the threat model and recovery story.
Master key custody → Multi-tier loader: PEGAPROX_DB_KEY env / systemd LoadCredentialEncrypted (TPM2-bound) / /etc/pegaprox/secret.key / ~/.config/pegaprox/secret.key / legacy config/. Default chmod 0600, files with loose permissions are skipped rather than used silently.
Sensitive fields (Cluster PW, SSH keys, TOTP secrets, OIDC client secrets, LDAP bind) → Fernet (AES-256-GCM equivalent), works even when full-DB encryption isn't available.
API Tokens → SHA-256 hash (constant-time compare).
Passwords → Argon2id (3 iter, 64 MB memory cost).
HTTPS required for production.
Session tokens expire after inactivity; optional strict-IP binding.
Per-IP rate limiting on login + every authenticated endpoint.
Input sanitization, CSRF Origin matching, RBAC enforced server-side on every route.
Auto-encryption on first boot - operators can opt out with PEGAPROX_DISABLE_AUTO_ENCRYPT=1 if they want to take their own pre-encryption backup first.
This project is licensed under the AGPL-3.0 License - see the LICENSE file for details.
Attribution (AGPL §7b): Under Section 7(b) of the AGPL, the "Powered by PegaProx" attribution shown in the client portal is a required author attribution and must be preserved in every copy and modified/derivative version — see the NOTICE file. Note also that AGPL §13 requires anyone hosting a modified version for network users to publish that version's complete source to those users. PegaProx is AGPL-3.0 only — the attribution applies to everyone, without exception.
Like most modern dev teams, we use AI-assisted tooling (code completion, docs generation, review automation, security audits). All architecture decisions, implementation, and testing are handled by our three-person team. - see IBM , IBM Case Studies , MIT Tech Review
AI-driven security auditing is an industry-standard practice - see Hacker News, IBM Research.
A self-hosted dashboard for visualizing Docker containers and network services. DockDash discovers services automatically, tracks their health, monitors container image updates, and lets you map connections between them on an interactive canvas.