Red Hat OpenShift on Oxide
When is Oxide the right infrastructure for self-managed Red Hat OpenShift clusters?
Clusters run on Oxide’s integrated rack design
No separate hypervisor layer to provision (custom)
Manual setup (UPI)
Hardware root of trust with trust-quorum key management built into the rack itself (see details)
Auditable, verifiable
Inherits server OEM’s firmware/BMC
No unified control
Capex
One-time purchase, no recurring fees or usage limits
Capex
Hardware purchase
Manual setup (UPI)
Installer provisions on top of existing vSphere layer (IPI-supported)
Installer provisions resources directly (IPI-native)
Clusters run on Oxide’s integrated rack design
No separate hypervisor layer to provision (custom)
Inherits server OEM’s firmware/BMC
No unified control
Inherits underlying hardware firmware
vSphere/NSX software-layer controls above
Provider-managed hardware root of trust
Audited but opaque
Hardware root of trust with trust-quorum key management built into the rack itself (see details)
Auditable, verifiable
Capex
Hardware purchase
Opex
VMware/Broadcom licensing
Opex
Consumption-based billing
Capex
One-time purchase, no recurring fees or usage limits
Talk to an expert to find out which of your workloads are best suited for Oxide.
Which Red Hat OpenShift clusters are ideal for Oxide?
Oxide is ideal for self-managed clusters that need locality, sovereignty, predictable infrastructure ownership, or an on-prem target. In particular:
Regulated, high-assurance workloads that demand air-gapped environments and can’t tolerate opaque BMC or firmware blobs
Stable-capacity, long-lived clusters like core platform services, internal PaaS, CI/CD backends, and data platforms
Any workloads you want to move off VMware so you can own your whole stack
Multi-tenant private cloud workloads that demand strong isolation guarantees
Why Oxide is a good target for Red Hat OpenShift clusters
The Oxide Cloud Computer is a complete, pre-configured rack-scale system (hardware, firmware, host OS, storage, and a hypervisor) that you own outright.
This is different from public cloud infrastructure targets because:
Secure by design
Every hardware and software component is deeply co-designed to be more secure, with a hardware root of trust that ensures attestation across the stack.
One vendor
The whole system is supported by the same vendor.
Owned outright
There are no recurring subscription fees.
It’s also different from commodity on-prem infrastructure because it gives you a true cloud-native experience. All compute, networking, and storage resources are available through a REST API.
For OpenShift clusters, this means you keep using the OpenShift CLI, Operators, GitOps, policy, and Red Hat subscriptions with Oxide as a standardized, API-driven infrastructure target.
Why Oxide is better than bare metal
Kubernetes wasn’t designed for bare metal implementations. Even though using bare metal removes virtualization overhead, it just creates new tasks related to managing the underlying hardware.
With Oxide, all that additional effort (such as firmware updates and hardware fault monitoring) gets taken care of as part of a unified product experience.
Oxide gives you VMs, VPC networking, disks, IPs, APIs, and infrastructure that you own, while OpenShift gives you RHCOS, Kubernetes, the application platform, policy, and developer workflows.
Oxide’s VMs are a helpful interaction surface between the hardware and your workloads.
Predictable economics
Hardware purchased outright with open source software. No surprise consumption bills or software subscription renewals.
One hand to shake
One Oxide team supports the whole stack, from firmware to control plane. No finger-pointing between vendors.
Verifiable infrastructure
Hardware root of trust with open source firmware. Every layer is verified from silicon up.
Your cloud tools, your infrastructure
Terraform, Kubernetes, and your existing automation: first-class, supported integrations, no lock-in.
Plus broad compatibility
Standard VMs mean your existing software runs without modification