Agentless console for Proxmox VE clusters and PBS servers
ProxCenter is a web console that brings several Proxmox VE clusters and Proxmox Backup Server (PBS) instances into one interface. The repository calls it an alternative to VMware vCenter for Proxmox, and the inventory borrows the vSphere tree: clusters, nodes, VMs, containers, storage, pools and tags. Its publisher, AdminSysPro, ships a free Community edition and a commercially licensed Enterprise edition.
Nothing gets installed on the Proxmox hosts. ProxCenter talks to the Proxmox VE API on port 8006 and to PBS on 8007, preferably with an API token, and finds the rest of a cluster from a single node. SSH is only used for disk imports, rolling updates, CVE scans and network flow collection.
Proxmox Datacenter Manager does the same job but comes from the company behind Proxmox. PegaProx, another third-party console, can also connect XCP-ng pools as a tech preview; in ProxCenter, XCP-ng is only a migration source. The comparison of multi-cluster consoles for Proxmox sets the third-party consoles against the vendor's own tool.
Inventory tree modeled on vSphere, down to Ceph OSDs
- An inventory modeled on vSphere: the tree follows the Proxmox topology, with extra views by host, pool and tag. Migrations in progress are picked up automatically.
- Ceph down to the OSD: the CRUSH tree and the state of every OSD. The Ceph overview is part of the Community edition.
- Several PBS servers in one console: the Community edition manages multiple Proxmox Backup Server instances and shows their backups.
- Browser consoles: noVNC and SPICE for QEMU guests.
- DRS (Enterprise): balances VMs across the nodes of a cluster on CPU, memory and storage, in manual, partial or automatic mode, with affinity and anti-affinity rules.
- Imports from other hypervisors (Enterprise): VMware ESXi and vCenter, Hyper-V, Nutanix AHV and XCP-ng. Warm (CBT) migration works from ESXi and vCenter, and from XCP-ng over a direct pool connection. It needs Proxmox VE 9 on the target node.
Migration and DRS need a per-node Enterprise license
Automation is Enterprise only. The Community edition has no node limit and covers inventory, storage and Ceph, backups, events and users. Migration, DRS, rolling updates, site recovery, RBAC with LDAP or OIDC, reports and multi-tenancy are Enterprise according to the documentation, although the README lists migration and "RBAC & SSO" without saying so. Those features need a closed-source orchestrator written in Go, so only the Community edition, under AGPL-3.0-or-later, builds from the repository.
Enterprise is billed per node. The EULA describes an annual subscription per managed node, and the website publishes no prices. A connected license holds a 30-day lease, renewed by a daily sync that sends the key, the version and the node count; past the node quota, the install turns read-only. The MSP mode (virtual datacenters, per-tenant quotas, IPAM) targets hosting providers, yet the EULA bars providing managed services to third parties without a separate written agreement.
PostgreSQL is required. The installer, which is the supported path, sets up Docker, Compose and PostgreSQL under /opt/proxcenter. The README asks for Docker Engine 24 or later, at least 2 GB of RAM and 10 GB of disk, and Proxmox VE 8.x or 9.x. Without Docker, the Community edition builds by hand with Node.js 22.12 and PostgreSQL 16 or later: 4 GB of RAM to build, about 300 MB to run.
Moving VMs between clusters goes through Proxmox. The documentation describes offline cross-cluster moves built on Proxmox's remote migration, which refuses guests that are HA-managed, replicated or carrying snapshots.
25 releases in seven months, one contributor. The repository dates from February 4, 2026. From v1.0.0 (March 1, 2026) to v1.4.11 (October 5, 2026), 25 versions shipped, and the adminsyspro account wrote 2,083 commits against 66 from Dependabot. Version 1.4.0 (May 12, 2026) swapped SQLite for PostgreSQL with no automatic data migration: upgrading starts from an empty database.