Full VM inventory
Every QEMU guest across the cluster: vCPU, memory, disks, partitions, networks, guest-agent tools, and snapshots, collected in parallel and projected into clean, sortable grids.
PVEViewer connects to your Proxmox VE clusters over the REST API and turns them into a rich, multi-tab Excel workbook and live, filterable grids for inventory, health, and capacity planning in one click. No agents to deploy. No history database. Just answers.
One connection, a full picture. PVEViewer pulls live data straight from the API. No agents to install, nothing to maintain.
Every QEMU guest across the cluster: vCPU, memory, disks, partitions, networks, guest-agent tools, and snapshots, collected in parallel and projected into clean, sortable grids.
One click produces a comprehensive multi-tab workbook: Info, CPU, Memory, Disk, Partition, Network, Tools, Snapshot, Host, Cluster, Storage, Health & metadata, ready for analysis and handoff.
Automatic rules flag orphaned volumes, missing or silent guest agents, stale snapshots, storage pressure, CPU/memory overcommit, quorum loss, expiring certs, and pending updates.
Add up to two clusters per site, save reusable connection profiles, and merge everything into a single workbook with a source-cluster column on every tab.
Capture each node's bare-metal recovery state over SSH: network, storage.cfg, /etc/pve, users, host keys, and package lists, with optional OpenSSL-compatible AES encryption and per-host restore notes.
Run scheduled, headless exports with a config file of saved profiles, perfect for nightly inventory snapshots dropped to a share. The GUI and CLI are separate, self-contained downloads.
If you've ever handed a stakeholder a virtualization inventory export, this will feel like home. PVEViewer gives every dimension its own tab for Proxmox: filterable, sortable, and ready to pivot.
Average & peak CPU/memory pulled from Proxmox RRD. No agent on the host needed beyond the QEMU guest agent already running in your VMs.
Point PVEViewer at any one node. Use an API token (recommended) or username/password with TOTP. Self-signed certs work out of the box. Save the profile for next time.
It fans out across the cluster's API and RRD metrics in parallel, collecting config, status, snapshots, guest-agent details, and utilization, then runs the health rules.
Browse live grids in the app, or export the full multi-tab workbook to share. Schedule the CLI to do it unattended on a timer.
Every capability is scriptable. Drop a config file of saved cluster profiles and let Task Scheduler produce a fresh inventory each night, straight to a file share. The same binary handles host backups and AES encrypt/decrypt.
.exe, no .NET install--selftest previews a workbook with zero infrastructure# nightly inventory for every saved cluster
PVEViewer.Cli.exe --config sites.json --out \\nas\reports
→ Cluster-A 4 nodes · 38 VMs collected
→ Cluster-B 2 nodes · 17 VMs collected
→ health rules: 7 findings
✓ PVEViewer_site_2026-06-29.xlsx (13 tabs)
# back up host configs for bare-metal recovery
PVEViewer.Cli.exe backup-hosts --encrypt --out D:\Backups
Free for Windows. Download, connect a cluster, and have a full inventory workbook in minutes.
Windows 10/11 · 64-bit · self-contained · GUI and CLI are separate single-file downloads
No. PVEViewer is an independent tool that talks to the Proxmox VE REST API. It is not affiliated with, endorsed by, or sponsored by Proxmox Server Solutions GmbH. "Proxmox" is a trademark of its respective owner.
No host-side agent. PVEViewer reads everything through the standard REST API and RRD metrics. The only requirement is the QEMU guest agent inside your VMs, which most Proxmox deployments already run for richer detail (IPs, filesystems, OS info).
An API token is recommended. Username/password with TOTP is also supported as a fallback. Self-signed certificates are expected and accepted by default.
Not in this version. PVEViewer focuses on QEMU/KVM virtual machines for capacity planning and inventory.
It's point-in-time by design. Every run is a fresh snapshot. Average and peak utilization come straight from Proxmox's own RRD data, so you still get trend context without a local database to maintain.
It's separate from VM backups. Over SSH it captures each node's configuration needed to rebuild it after a clean reinstall: network, storage.cfg, /etc/pve, users, SSH host keys, and package lists, with optional AES encryption and generated restore instructions. It does not replace vzdump or Proxmox Backup Server.