pvecli didn’t start as a product, but as a solution to a very practical problem. And isn’t that how many good products begin?
Sometimes a client doesn’t need another person on the team, but someone capable of removing a problem that costs the entire team time every single day.
If you manage a similar infrastructure, the next few lines may be useful to you. Here’s how we actually got here:
pvecli started with one specific problem faced by a DevXo client — a hosting company managing several Proxmox VE environments across more than one data center.
As the infrastructure grew, something that had initially seemed like a routine administrative task gradually began taking up far too much time.
Engineers were switching between different Proxmox environments, manually checking which node a particular virtual machine was running on, and using SSH for operations that were difficult to fit into an automated workflow.
Proxmox itself had the necessary functionality.
What was missing, however, was one thing — a unified and predictable way to manage and automate the entire process.
Backup management.
Migrations and cloning.
Snapshots.
Tracking Proxmox tasks.
Real-time resource monitoring.
Working with multiple separate Proxmox environments.
And at some point, it became clear that the problem we were solving wasn’t actually specific to that company.
It is familiar to many teams managing growing Proxmox infrastructure.
So we spun off pvecli as a standalone open-source project by DevXo and continued developing it as a tool that can be used by system administrators, DevOps teams, and managed service providers.
As it evolved, we also added things that went beyond the original client scope — multi-cluster configuration, security checks with CodeQL, govulncheck, and staticcheck on every commit, as well as automated smoke tests against real infrastructure, designed to validate releases without putting the production environment at risk.
For us, pvecli is interesting not only as an open-source project.
It is a good example of the way we work at DevXo: we start not with the technology, but with the real problem.
We understand what slows the team down, what is difficult to automate, and where unnecessary risk is being created. Then we build the solution around the real workflow.
Sometimes that means an internal tool, other times an integration or an entire platform.
And sometimes a solution created for one client turns out to be useful to many others.
pvecli was exactly that kind of case.
📞 Contact our team to see how we can help.