SUSE Rancher on Oxide

When is Oxide the right infrastructure for self-managed SUSE Rancher clusters?

On bare metal vs. On VMware vs. On public cloud vs. On Oxide
On Oxide
On bare metal
Provisioning model

Clusters run on Oxide’s integrated rack design

No separate hypervisor layer to provision (read our guide)

Manual setup

Security/root of trust

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

Hardware cost model

Capex

One-time purchase, no recurring fees or usage limits

Capex

Hardware purchase

On bare metal
On VMware
On public cloud
On Oxide
Provisioning model

Manual setup

Installer provisions on top of existing vSphere layer

Installer provisions resources directly

Clusters run on Oxide’s integrated rack design

No separate hypervisor layer to provision (read our guide)

Security/root of trust

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

Hardware cost model

Capex

Hardware purchase

Opex

VMware/Broadcom licensing

Opex

Consumption-based billing

Capex

One-time purchase, no recurring fees or usage limits

Learn more about SUSE Rancher on Oxide

Talk to an expert to find out which of your workloads are best suited for Oxide.

Contact us directly at sales@oxide.computer

Which clusters are ideal for Oxide?

Oxide makes sense for multi-cluster teams that want to combine Rancher and a conventional supported Linux node OS. It’s ideal for self-managed clusters that need locality, sovereignty, predictable infrastructure ownership, or an on-prem target.

Regulated, high-assurance workloads that require air-gapped environments (especially if they can’t tolerate opaque BMC/firmware)

Stable-capacity, long-lived clusters like core platform services, internal PaaS, CI/CD backends, and data platforms

Workloads you want to move off VMware (with Oxide, you own your whole stack, so you can move away from subscription licensing)

Multi-tenant private cloud workloads that demand strong isolation guarantees

Why Oxide makes sense for SUSE Rancher clusters

The Oxide Cloud Computer is a rack-scale system that gives you standardized, pre-configured hardware, firmware, and storage.

It’s built with deep co-design between hardware and software, so the entire system is auditable. It’s also secured by a hardware root of trust that ensures attestation across the stack.

Crucially, you own the infrastructure outright.

You get a cloud-native experience (compute, networking, and storage resources are all available through a REST API) on on-prem infrastructure without recurring subscription fees.

In practice, that means you can standardize infrastructure across multiple, heterogeneous clusters, and move to a more predictable economic model.

How it works

API-driven provisioning

Rancher provisions infrastructure through an API as part of the cluster workflow.

Elastic VM nodes

Machine pools and Oxide credentials create, scale, and remove VM nodes in your project, VPC, and subnet.

Your team runs the clusters

Your team manages Rancher and RKE2 operations.

Declarative cluster definitions

Cluster definitions live in Kubernetes manifests or the Rancher UI. Oxide provides a secure cloud substrate.

Infrastructure-aware nodes

The Oxide cloud controller manager supplies provider IDs, addresses, labels, node health, and floating-IP-backed load balancer services, so cluster state stays connected to infrastructure.

Your choice of node OS

Rancher preserves node-OS choice, and the driver uses an RKE2-supported Linux image.

Joint support

Supported by both Oxide and SUSE.

Why Oxide is better than bare metal

With Oxide, all the additional effort of managing hardware (such as firmware updates and hardware fault monitoring) is taken care of as part of a unified product experience.

In practical terms, when you run multiple Rancher clusters, Oxide VMs are a helpful interaction surface between your hardware and your workloads.

Oxide gives you elastic VM, disk, VPC, and IP infrastructure. Meanwhile, Rancher uses an Oxide-maintained external node driver to create, scale, and remove RKE2 nodes.

Additionally, the Oxide cloud controller manager adds infrastructure-aware node data and floating-IP service exposure, so you can design around support, load-balancing, and storage limits.

Predictable economics

Hardware purchased outright with open source software. No surprise consumption bills or software subscription renewals.

Cost comparison graph showing Oxide savings over time

One hand to shake

One Oxide team supports the whole stack, from firmware to control plane. No finger-pointing between vendors.

Oxide console support bundle with the Send to support action

Verifiable infrastructure

Hardware root of trust with open source firmware. Every layer is verified from silicon up.

Hardware root of trust boot chain diagram
Fig. 1
Root of trust

Your cloud tools, your infrastructure

Terraform, Kubernetes, and your existing automation: first-class, supported integrations, no lock-in.

Official integrations

Plus broad compatibility

Standard VMs mean your existing software runs without modification

Pulumi logoPulumi
Prometheus logoPrometheus
Grafana logoGrafana
GitHub logoGitHub Actions
GitLab logoGitLab CI
REST API Tools

Run SUSE Rancher on the cloud you own