Rancher Labs started (2014) as a container-management company and, after Kubernetes won the orchestration war, pivoted to a simple thesis: most organizations will run many Kubernetes clusters, in many places, from many vendors, and they need one control plane to govern all of them. SUSE acquired Rancher Labs in December 2020 and has since grown the portfolio into a full stack:
- Run Kubernetes anywhere — K3s (edge/small), RKE2 (hardened, datacenter/government).
- Manage it all from one place — Rancher Manager.
- Deliver apps declaratively — Fleet.
- Persist data — Longhorn.
- Secure it — NeuVector, Kubewarden, CIS benchmarking.
- Manage the OS too — Elemental, SLE Micro.
- Run VMs next to containers — Harvester (commercially branded SUSE Virtualization within Rancher Prime).
The unifying design idea: everything is a Kubernetes controller reconciling CRDs. Clusters, OS images, VMs, networks, volumes and Git repos are all custom resources. Once you internalize that, the whole stack becomes learnable with the same kubectl get/describe/logs muscle memory.
Community vs. Prime¶
Everything covered here is open source (mostly Apache 2.0). Rancher Prime is SUSE's commercial subscription: supported builds, a trusted image registry, longer support windows, SUSE Observability, and enterprise support. Functionally the community and Prime bits are close; the differences are support, SLAs, signed artifacts and some Prime-only UI extensions.