A genuinely capable platform, built for container-native workloads first, with virtualization added on top. Where that complexity actually goes, and what it costs.
Of that $3,414,720/year, $3,072,000 is Red Hat OpenShift Virtualization's own license and $342,720 is 5,040 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).
Red Hat is a very credible product offering: it's also super complicated and super expensive, because virtualization is added to a platform built for something else.
Every legacy hypervisor’s per-cluster management burden (configuration, security, per-cluster images) is still there underneath Kubernetes.
You now also need to stand up, secure, and operate the container infrastructure itself, whether or not you run a single container workload.
One control plane, built for virtualization: not virtualization bolted onto a platform designed for containers.
OpenShift Virtualization is a real, high-quality platform: it's just designed for cloud-native application deployment, with virtualization shoehorned in rather than built for it first. That design choice shows up in what it takes to run.
Container-orchestration expertise becomes a prerequisite for running VMs, not a byproduct: the same control-plane overhead every legacy hypervisor has, plus a container platform’s own.
Harder to deploy and administer than a purpose-built hypervisor, and priced for that specialization.
One control plane designed around running VMs: not virtualization added to a platform built for something else.
The same five questions every one of these environments eventually has to answer.
| Basalt | Red Hat OpenShift Virtualization | |
|---|---|---|
| Licensing model | Flat, deployment-scoped | Subscription tier, priced per core pair |
| Consolidation penalty | None: fewer hosts costs less | Yes: scales with the subscription tier |
| Underlying core | KVM + Rust | KVM, via KubeVirt |
| Edge & disconnected sites | Built for constrained, disconnected sites | Needs the full container-platform stack |
| Support model | One assigned engineer, not a ticket queue | Red Hat–certified specialists required |
That's a reasonable instinct: moving off Red Hat 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.