The bargain changed after you had standardized. This is what a credible, tested alternative looks like before the next renewal.
Of that $441,600/year, $245,760 is VMware's own license and $195,840 is 2,880 hours of estimated management overhead at $68/hour, fully loaded (U.S. Bureau of Labor Statistics), not just the sticker price.
Your own assumptions, live, not a quote for either platform. Basalt is $800 per server, per year, up to 100 servers; above that it's a custom quote (see Pricing & licensing).
VMware's own security-hardening cycle is the clearest picture of what a control plane per cluster actually costs in labor: not licensing, hours.
A hypervisor STIG, an application STIG, and a database STIG, each applied and scanned separately, and applying one often breaks something else on top of that.
A hundred vCenter instances means a hundred copies of the same 20–30 images to patch and secure, on the same standard, one distributed cluster at a time.
One global control plane means one place to secure and patch, not a hundred: the management-cost line above reflects that, not just the license.
Standardizing on it was the right call, and stayed right for a long time. “The standard, nobody gets fired for buying it” is a fair description of where it sits today.
Renewal increases widely reported since the Broadcom acquisition, licensing consolidated into fewer bundles, and paid features many sites never use.
Public sentiment about the pricing changes runs heavily negative: customers describe staying out of fear of a migration project, not preference for the product.
Deployment-scoped licensing, and a two-node edge site without a third arbitration node.
A tested alternative in hand changes the conversation at the next renewal even if you never move a workload.
The same five questions every one of these environments eventually has to answer.
| Basalt | VMware | |
|---|---|---|
| Licensing model | Flat, deployment-scoped | Per-core |
| Consolidation penalty | None: fewer hosts costs less | Yes: renewal scales with the infrastructure |
| Underlying core | KVM + Rust | ESXi (proprietary) |
| Edge & disconnected sites | Built for constrained, disconnected sites | Not edge-optimized |
| Support model | One assigned engineer, not a ticket queue | Enterprise support tiers |
That's a reasonable instinct: moving off VMware is the right call either way. Just know the management layer doesn't change with any of them.
Free to download, but teams running it in production pay for the support subscription, and someone still has to physically show up to a remote cluster, or open a VPN exception to reach it: the same control-plane-per-cluster overhead.
Per-socket pricing on top of a hardware tie, with the same per-cluster control plane every legacy hypervisor carries.
Built on the same open-source KVM core Basalt is, but the per-cluster control plane, and the hours it takes to run, don’t go away.
Run the numbers with your own infrastructure, then put Basalt beside your incumbent in a controlled environment, with a rollback story written down before anything moves.