> Something like ProxMox that has no third party support, no veeam support, limited automation tooling, limited support for commerical monitoring (like PRTG) etc etc is probally a non-starter unless those things support it.
Proxmox VE has an extensive REST API with API tokens and an access control system to allow for safe automation.
There are also Terraform providers and Ansible modules for those that do not want to use the API directly, or use those automation tools already.
There's also Proxmox Backup Server that can handle guest-level backups as good as Veeam can, but yes, the agents and application level backups is still not there, but most of those are unrelated to the outer hypervisor, so one can still use their preferred backup solution for those parts just fine.
Central monitoring is possible through the external metric server integration.
Further third-party integration is a natural chicken-and-egg issue.
For a lot of third party integrations you might just need to ask the vendor of said third party if they can support Proxmox VE, as long as they receive no inquiries as admins won't even ask if it would be possible, they have no incentive to add support for anything.
But it's getting better, and more eggs are hatching.
> It would cost us far far far far more than 3x licensing increases to git rid vmware. Broadcom knows this.
The migrations I saw in our enterprise support had way lower cost. IMO 3x the cost would need some heavily specialized workload (which IME fewer admins actually really have than they might think) and/or admins that are just heavily against any change (as yes, they must relearn how to do some things, there are training courses for a few thousand bucks that cover the whole stack though) or having an anti-FOSS/Linux'ish mindset. I.e., come to us with so many prejudices that it's hard to make them realize that, while there are surely things that can improve, that just the same on the other side of the "pasture", but overall the grass is quite green enough for most use cases already.