We use analytics cookies and anonymised session recordings to improve the product. Do you accept?

Proxmox VE Coverage

Inventory and cost visibility for QEMU VMs and LXC containers on your own Proxmox VE cluster.

2 min read

How it works

Inventory, metrics and optimization run today, priced from rates you set yourself — there is no price list to pull from self-hosted hardware.

Inventory
Discovers every QEMU VM, LXC container and template, each physical node, every datastore and individual disk volume across the cluster, on a schedule or on-demand.
Cost estimation
Priced from the $/vCPU, $/GB RAM and $/GB disk monthly rates you set on the account — VMs and containers are billed on all three; templates only on disk space; nodes and datastores carry no cost of their own; an orphan volume is billed on disk alone, since nothing else accounts for it.
Optimization
Flags stopped VMs/containers still reserving resources, running ones underutilized on CPU and memory, nodes with unassigned physical capacity, datastores running low or nearly empty, and orphan volumes left behind by a deleted VM/container.

Coverage by service

One card per service. Each card lists its resource types and the capabilities they support.

Inventory Metrics Optimization Drift detection
Storage
2 resource types
  • Datastores
  • Volumes
Compute
2 resource types
  • Nodes
  • VMs & Containers

API token & permissions

One token, restricted to the built-in read-only role — covers every node in the cluster.

  1. In the Proxmox VE web UI, go to Datacenter → Permissions → Users and create a dedicated user (e.g. pruneops@pve), or reuse an existing one.

  2. Under Datacenter → Permissions, add a permission for that user on path / (propagated to all nodes/VMs) with role PVEAuditor — Proxmox's built-in read-only role. No write access is ever needed.

  3. Under Datacenter → Permissions → API Tokens, add a new token for that user (e.g. token ID pruneops). Uncheck Privilege Separation so the token inherits the user's PVEAuditor role directly, or grant PVEAuditor to the token itself the same way as above.

  4. Copy the token ID (user@realm!tokenid, e.g. pruneops@pve!pruneops) and secret — the secret is shown only once.

Connect the cluster

  1. Go to Organization → Integrations → Cloud Accounts → Add Account, pick Proxmox VE.

  2. Enter the Host (any cluster node's address, e.g. pve.example.com:8006) and the Token ID / Token Secret from above. Leave Verify TLS certificate off unless the cluster has a certificate signed by a trusted CA — most run with the built-in self-signed one.

Set your pricing

On the account's own Pricing tab, once saved.

Proxmox runs on your own hardware, so there's no price list to pull. Open the account's Pricing tab and set your own $/vCPU, $/GB RAM and $/GB disk monthly rates — every VM/container's cost is estimated from these rates and its allocated specs; templates are billed on disk only, since they never run.

First sync

Once the account is saved, inventory runs on the next hourly cycle — or trigger it immediately from the account's detail page. Discovered VMs, containers and templates appear under Audit → Proxmox.