Hello Proxmox community,
I’d like to share an open-source project I maintain: Proxbox, a NetBox plugin for synchronizing Proxmox VE infrastructure data into NetBox.
The goal is simple: keep NetBox updated with inventory data from real Proxmox environments, so Proxmox clusters, nodes, VMs, containers, storage, backups, snapshots, interfaces, and IP addresses can be reflected inside NetBox.
- Project repository:
https://github.com/emersonfelipesp/netbox-proxbox - Documentation:
https://emersonfelipesp.com/netbox-proxbox/
Current capabilities include:
- Proxmox cluster and node inventory
- VM and LXC container synchronization
- Storage and virtual disk synchronization
- Network interfaces and IP address discovery
- VM backups and snapshots
- Backup routines / vzdump schedules
- Replication jobs
- HA status visibility
- VM task history
- VM cloud-init data
- Scheduled sync through NetBox background jobs
- Real-time sync progress through SSE
- Separate FastAPI backend: proxbox-api
- Support for Proxmox VE 7.x, 8.x, and 9.x
- Support for NetBox 4.5.x and 4.6.x
A few clarifications:
- Proxbox is focused on inventory synchronization and discovery.
- It does not try to replace the Proxmox VE UI.
- Metrics such as CPU, memory, and uptime are captured as point-in-time data during sync, not as continuous monitoring.
- For Proxmox VE 9, the API role needs VM.GuestAgent.Audit if you want VM IP discovery through the QEMU guest agent.
The project uses a separate backend service, proxbox-api, which talks to Proxmox and NetBox. The NetBox plugin stores the endpoint configuration and triggers sync jobs from the NetBox UI.
I’m sharing it here because Proxmox + NetBox is a common gap for people who want better infrastructure inventory, especially in environments where NetBox is already used as the source of truth for DCIM/IPAM.
Feedback, issues, and contributions are welcome.
