What is it?
Proxmox Datacenter Manager (PDM) is the central console that Proxmox Server Solutions, the company behind Proxmox VE, ships for watching over many installations from one web interface. You register standalone nodes, Proxmox VE clusters and Proxmox Backup Server instances, which PDM calls "remotes". It collects their metrics and task logs, and hands you off to each remote's own interface for detailed configuration. If the console goes down, the remotes keep running.
PegaProx and ProxCenter are third-party consoles built for the same job. PDM comes from the vendor itself, and existing Proxmox subscriptions include support for it.
The comparison of multi-cluster consoles for Proxmox sets PDM against the third-party consoles on cross-cluster migration, backups and the access each one needs.
Why is it interesting?
- Live migration across clusters: a VM or LXC container moves from one remote to another, and the 1.0 announcement states that the two clusters need no shared cluster network.
- Every guest in one list: since 1.1, the VMs and containers of all remotes sit in a single table you can filter with
tag:,remote:orstatus:, with start, shutdown, migration and snapshot actions on each row. - Fleet updates: one panel lists pending packages on every remote and installs them through the remote shell, which needs Proxmox VE 9.1 or PBS 4.1.
- Proxmox Backup Server support: since 1.0, a PBS instance is a remote like any other, with its datastores, their usage and its metrics on the dashboard.
- Delegated views: a user can be given a filtered view without any permission on the remotes behind it. Login goes through LDAP, Active Directory or OpenID Connect.
- Ceph and networking: 1.1 tracks the health of hyper-converged Ceph clusters, and the EVPN settings create zones and VNets across several remotes at once.
Good to know
Proxmox remotes only. PDM manages Proxmox VE 8.4 or later and Proxmox Backup Server 3.4 or later. The only new remote type on the roadmap is Proxmox Mail Gateway. PegaProx also handles XCP-ng pools.
A dedicated machine on Debian 13. The ISO is the recommended install, the packages also go on top of Debian Trixie, and the 1.0 announcement advises against putting PDM on a Proxmox VE or PBS host. For production, the docs recommend 2 cores, 4 GiB of RAM and 40 GB on hardware RAID or redundant ZFS. ProxCenter's installer, by contrast, sets up Docker and PostgreSQL.
No dedicated subscription, but an 80% threshold. The enterprise repository and support come with Basic or higher subscriptions on your remotes, provided at least 80% of the configured nodes hold one. Below that, you get the pdm-no-subscription repository, which the docs reserve for testing and non-production use.
Migration rests on an experimental feature. To move a guest to another cluster, PDM calls the Proxmox VE remote-migrate API (server/src/api/pve/qemu.rs), and the Proxmox VE documentation still labels qm remote-migrate an "EXPERIMENTAL feature!".
Stable since December 2025. Version 0.1 alpha shipped on December 19, 2024, 0.9 beta on September 11, 2025, 1.0 on December 4, 2025 and 1.1 on May 28, 2026. The Debian changelog in the repository stops at 1.1.7, dated July 15, 2026, and the latest commit is from October 5, 2026. The code is Rust down to the WebAssembly frontend, and GitHub only hosts a read-only mirror of git.proxmox.com.
Still missing. The roadmap lists bulk actions on guests, backup job tracking and firewall management. An active-standby setup for PDM itself is under evaluation.