Proxmox Datacenter Manager Alpha: Setup Guide

Managing a single Proxmox VE node is straightforward. Managing multiple clusters? That's where things get messy — until now. Proxmox Datacenter Manager (PDM) is Proxmox's answer to multi-cluster sprawl, and its alpha release is already turning heads in the homelab and enterprise communities. If you've been running two or more Proxmox clusters and dreaming of a single pane of glass, this guide walks you through installing and configuring PDM from scratch.

What Is Proxmox Datacenter Manager?

Proxmox Datacenter Manager is a standalone web application that sits above your Proxmox VE clusters and provides a unified management interface. Think of it as a control plane for your control planes.

Unlike Proxmox's built-in cluster management — which requires all nodes to share the same corosync cluster — PDM works across completely independent clusters. Your homelab cluster, an offsite backup node, and a future production cluster can all be managed from one place.

Key capabilities in the current alpha include:

Multi-cluster overview — See all connected clusters, their nodes, and health status at a glance
Centralized VM and container inventory — Browse VMs and LXC containers across every connected cluster
Cross-cluster resource monitoring — CPU, memory, and storage usage rolled up at the datacenter level
Unified user and permission management — Manage access control across clusters from a single interface
Remote console access — Open VM consoles directly from the PDM dashboard

This is still alpha software, so expect rough edges. But even in its current state, PDM is genuinely useful if you're running multiple Proxmox installations.

Prerequisites

Before you start, make sure you have:

A Debian 12 (Bookworm) machine to install PDM on — a VM, LXC container, or bare-metal server works fine. It does not need to be a Proxmox node itself.
At least one running Proxmox VE 8.x or 9.x cluster to connect
Network access from the PDM host to your Proxmox API endpoints (port 8006)
A Proxmox API token with sufficient permissions (or root credentials for initial testing)
Basic familiarity with Debian package management and systemd

PDM is lightweight. A 2-core VM with 2 GB of RAM running Debian 12 is more than enough for most homelab setups.

Installing Proxmox Datacenter Manager

Step 1: Prepare the Debian Host

Start with a minimal Debian 12 installation and update the system:

apt update && apt full-upgrade -y

Install the required dependencies:

apt install -y curl gnupg2 ca-certificates

Step 2: Add the Proxmox Repository

PDM is distributed through the Proxmox repository infrastructure. Add the GPG key first:

curl -o /etc/apt/trusted.gpg.d/proxmox-release-bookworm.gpg \
  http://download.proxmox.com/debian/proxmox-release-bookworm.gpg

Now add the PDM alpha repository:

echo "deb http://download.proxmox.com/debian/pdm bookworm pdm-alpha" \
  > /etc/apt/sources.list.d/pdm.list

Update your package list to pull in the new repo:

apt update

Step 3: Install PDM

Install the Proxmox Datacenter Manager package:

apt install -y proxmox-datacenter-manager

This pulls in all required dependencies, including the PDM web interface and backend services. A systemd service is created automatically.

Verify the service is running:

systemctl status proxmox-datacenter-manager

If it isn't active, start and enable it:

systemctl enable --now proxmox-datacenter-manager

Step 4: Access the Web Interface

PDM runs on port 8007 by default — chosen specifically to avoid conflicting with Proxmox VE's port 8006. Open your browser and navigate to:

https://:8007

You'll see an SSL certificate warning since PDM uses a self-signed cert out of the box. Accept it and proceed to the PDM login screen.

The default superuser is root with the password set during Debian installation. Log in and you're ready to start connecting clusters.

Connecting Proxmox VE Clusters

Creating an API Token in Proxmox VE

It's best practice to create a dedicated API token for PDM rather than using root credentials. In your Proxmox VE web UI:

Go to Datacenter → Permissions → API Tokens
Click Add
Select the user (e.g., root@pam) and give the token a name like pdm-token
Uncheck Privilege Separation if you want full access, or assign granular roles manually
Click Add and copy the token secret — you won't see it again

At minimum, the token needs these privileges for PDM to function:

VM.Audit — list and monitor VMs
Sys.Audit — monitor node status
Datastore.Audit — view storage usage
Pool.Audit — read pool configurations

For full management (start/stop VMs, open consoles), grant PVEAdmin at the datacenter level.

Adding a Remote in PDM

Back in the PDM interface, navigate to Remotes in the left sidebar. Click Add Remote and fill in the details:

Name: A friendly label for this cluster (e.g., homelab-main)
Host: The IP or hostname of any node in the cluster
Port: 8006 (Proxmox VE default)
User: root@pam or the user tied to your API token
Token: The API token ID in the format root@pam!pdm-token
Secret: The token secret you copied earlier

Click Test Connection to verify PDM can reach the cluster. If the test passes, click Add.

Repeat for each Proxmox VE cluster or standalone node you want to manage. PDM handles both single-node setups and multi-node corosync clusters equally well.

Exploring the PDM Interface

Once you've added a few remotes, the PDM dashboard starts showing its value.

Datacenter Overview

The main dashboard gives you a bird's-eye view of everything connected. You'll see total node count across all remotes, aggregate CPU and memory usage, running VM and container counts, and storage pool summaries.

This is the single-pane-of-glass moment — seeing your entire infrastructure without tab-hopping between multiple Proxmox UIs.

Unified VM and Container Inventory

Navigate to Virtual Machines or Containers to see a consolidated list across all connected clusters. Each row shows the VM or container name, its remote cluster, the node it's running on, current status, and resource usage.

You can filter by remote, status, or search by name. This is especially useful when you have dozens of workloads spread across multiple nodes. From this view you can perform basic operations: start, stop, reboot, and open the console.

Cross-Cluster Resource Monitoring

The Monitoring section provides aggregated metrics — CPU, memory, and storage trends per remote or rolled up at the datacenter level. It's not a Grafana replacement, but having a quick health overview without a full monitoring stack is genuinely convenient for smaller setups.

What PDM Can't Do Yet

Going in with realistic expectations is important. The alpha has meaningful gaps:

No cross-cluster migration — You can't live-migrate VMs between different PDM remotes. PDM is a management overlay, not a unified hypervisor. Moving workloads between independent clusters still requires manual backup and restore.

Limited VM lifecycle operations — Creating VMs, modifying hardware, and managing storage still require logging into the individual cluster UI. PDM's operations are largely read-only or basic start/stop/console.

No HA management — High Availability configuration remains per-cluster. PDM has no visibility into or control over HA groups and fencing.

Local authentication only — PDM manages its own user database. LDAP, Active Directory, and Proxmox VE user store integration are not yet implemented.

Basic networking visibility — VLAN configuration, Linux bridge management, and SDN are entirely absent from PDM. These remain per-cluster operations.

None of these are dealbreakers for alpha software. The roadmap points toward cross-cluster migration and richer lifecycle management in stable releases.

Security Hardening for PDM

Running PDM means running another web-accessible management service. Lock it down immediately:

Change the default password — Set a strong, unique password for the root account on first login.

Restrict network access — Put PDM behind a firewall rule so port 8007 is only reachable from trusted networks or your VPN. Never expose it directly to the public internet.

Use API tokens, not root credentials — Scoped tokens limit blast radius if the PDM host is ever compromised.

Reverse proxy with a real certificate — For any persistent deployment, front PDM with NGINX and a proper TLS certificate:

server {
    listen 443 ssl;
    server_name pdm.yourdomain.local;

ssl_certificate     /etc/letsencrypt/live/pdm.yourdomain.local/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/pdm.yourdomain.local/privkey.pem;

location / {
    proxy_pass         https://127.0.0.1:8007;
    proxy_ssl_verify   off;
    proxy_set_header   Host $host;
    proxy_set_header   X-Real-IP $remote_addr;
    proxy_http_version 1.1;
    proxy_set_header   Upgrade $http_upgrade;
    proxy_set_header   Connection "upgrade";
}

}

Keeping PDM Updated

Since this is alpha software, updates arrive frequently with bug fixes and new features. Keep PDM current with the standard Debian upgrade path:

apt update && apt upgrade proxmox-datacenter-manager

The service restarts automatically after package upgrades. Monitor the official Proxmox forum thread for the PDM alpha announcement to track breaking changes and release notes before upgrading in a critical environment.

Practical Use Cases

Even with alpha limitations, PDM solves real problems:

Multi-site homelab operators — If you run Proxmox at home and at a colocation or friend's location, PDM gives you a single monitoring dashboard without VPN-hopping between management UIs.

VMware escapees — Organizations migrating off VMware vCenter often cite multi-host management as the biggest Proxmox gap. PDM isn't vCenter parity yet, but it's a credible starting point.

Growing homelabs — When you spin up a second Proxmox cluster, PDM prevents dashboard fragmentation before it becomes a habit. Get it in place early.

Incident triage — Seeing all node health states in one place means you'll spot a struggling node faster than if you only check individual UIs when something's already broken.

Conclusion

Proxmox Datacenter Manager fills a genuine gap that Proxmox users have been asking about for years. Jumping between browser tabs to track which cluster hosts which workload is tedious — and it only gets worse as your infrastructure grows.

Even in alpha, PDM delivers a useful unified inventory, basic VM operations, and cross-cluster health monitoring. Yes, it can't yet do live cross-cluster migration or full VM lifecycle management. But for homelabbers and small shops running two or more Proxmox clusters, it's already worth deploying today.

Install it now, get comfortable with the interface, and you'll be ahead of the curve when the stable release lands with the full feature set. Proxmox has a strong track record of iterating quickly once an alpha ships — and the community feedback loop on this one is already moving fast.