Is Syself Autopilot a Rancher alternative?

For Kubernetes on Hetzner, yes. Rancher is a console for clusters on many providers, and you run Rancher and the clusters. Syself Autopilot is a managed service in which Syself does the platform work on Hetzner Cloud and bare metal.

Does Rancher support Hetzner?

Rancher can manage any conformant cluster, including one on Hetzner. It has no built-in Hetzner node driver, so Hetzner Cloud machines need a community driver, and bare-metal servers join as custom nodes you set up yourself.

Can we run our databases on Hetzner bare metal?

Yes. A bare-metal server includes its NVMe disks, and traffic on the default 1 Gbit uplink is unlimited. Databases run on those disks under an operator such as CloudNativePG, and KubeVirt runs virtual machines on the same servers. You run the databases, or an agency runs them for you in your cluster.

Who is on call for us, around the clock?

Syself Autopilot first handles node failures itself: it reboots a failed Hetzner Cloud node, replaces it if it doesn’t recover, and on bare metal tells you what broke when the hardware is at fault. Syself Autopilot includes support from the Syself team on business days; Premium Support adds a custom SLA and 24/7 cover. With self-hosted Rancher you are on call, and Rancher Prime adds 24x7 support from SUSE.

How does security compare?

RKE2 has CIS-hardened defaults and a DISA STIG; Rancher scans against CIS. Patching stays with you: tracking CVEs, testing fixes and rolling them out to every node, at least monthly. Syself checks each CVE against each release’s SBOM and ships fixes in a release built and tested as one; one with an overdue CVE does not ship. Syself Linux is read-only, and nodes need no private network.

How do upgrades compare?

On both, you decide when. Rancher rolls the nodes to the version you pick, and restoring an etcd snapshot rolls it back. Syself ships tested updates every week; you trigger one and Syself replaces nodes one at a time. There is no rollback, so a stalled upgrade is fixed forward.

Rancher is free. Why pay for Syself Autopilot?

With Rancher you still run the Rancher server, patch the node OS, set up Hetzner servers and upgrade the Hetzner integrations. Syself does that work for a platform fee plus a usage-based fee tied to your infrastructure spend, not to nodes or clusters. Try the pricing calculator.

What stays with my team on Syself Autopilot?

Your workloads and data, backups, GitOps, etcd encryption, OIDC and RBAC, SSH lockdown, network policies, logs and metrics. The shared-responsibility page lists every item.

Can we move from Rancher to Syself Autopilot?

Your workloads move as to any conformant cluster: manifests, Helm charts and data are standard Kubernetes. Rancher features such as Projects, Fleet bundles and SUSE Security (NeuVector) policies need a replacement.

What if we only use RKE2 or K3s, without Rancher?

Then you compare a distribution you run with a managed service. See Syself Autopilot vs RKE2 and K3s.

Syself Autopilot vs Rancher: Which Is Right for Your Kubernetes on Hetzner?

Rancher is free and gives you one console for clusters on many providers. You still run the Rancher server, set up each Hetzner server, patch every node and test each upgrade. With Syself Autopilot, Syself does that work on your own Hetzner servers.

What it is: Rancher is SUSE’s open-source console for Kubernetes clusters on many providers, such as EKS, AKS, GKE, vSphere or any cluster you import.²³
Who does the work: You usually install and run it, and the clusters under it. You patch the Linux on every node and keep the community Hetzner driver working.¹⁷¹⁵ SUSE sells a hosted version and 24x7 support under Rancher Prime.¹⁶¹⁸
Where it runs: It isn’t built for Hetzner: Hetzner Cloud servers come through a community driver, and bare-metal servers join as custom nodes you set up yourself.¹⁵

What it is: A managed service run by Syself: upstream Kubernetes on Syself Linux, its own node OS, built and tested with the in-cluster components as one release.¹³² It replaces failed cloud nodes and tells you what broke when bare-metal hardware fails.⁴¹⁰
Who does the work: Syself builds and patches the node OS, sets up each Hetzner server, checks every CVE against each release and tests every release on real clusters.³¹⁹³⁰²⁰ You decide when to roll out each Cluster Stack release.
Where it runs: Hetzner Cloud and bare-metal servers in your own Hetzner account, so the servers and the data stay yours.¹

Which One Fits You?

Tick what applies. The answer includes the needs where Rancher is the better choice.

Rancher · 0Syself Autopilot · 0

Tick what applies to you

The answer updates as you go. Every need on the list counts, including the ones that point away from us.

Syself Autopilot vs Rancher at a Glance

One short fact per side, each linked to its source.

Theme	self-run	fully managed, on your servers
Delivery model	Rancher Open-source software you install and run; SUSE also sells a hosted Rancher Prime¹⁶	Syself Autopilot A managed service; Syself runs the management cluster and the cluster lifecycle¹
Hetzner support	Rancher No built-in Hetzner node driver; community drivers for Hetzner Cloud, bare-metal servers join as custom nodes¹⁵	Syself Autopilot Built for Hetzner Cloud and bare metal; Syself installs each node from the rescue system, so it boots with nothing to download or configure¹⁹
Operating system	Rancher Any modern Linux you choose and patch, or SUSE’s SL Micro managed through Elemental¹⁷	Syself Autopilot Syself Linux, from release 1.36: about 350 MB, read-only, checked block by block, replaced rather than patched. A security team tracks each CVE, checks whether your clusters are exposed and ships the fix in a tested release; support is included³
Kubernetes	Rancher RKE2 or K3s, or a cluster you import²³	Syself Autopilot Upstream Kubernetes in a tested Cluster Stack release that pins the OS and components²
Upgrades	Rancher Pick a version in the UI and Rancher rolls the nodes; roll back by restoring an etcd snapshot¹³	Syself Autopilot Tested updates every week, listed in the Version Hub; you trigger one and Syself drains, removes and replaces each node, with no rollback²⁶
Testing	Rancher SUSE tests RKE2 on supported operating systems; the Hetzner driver, integrations and your settings are yours to test³⁴	Syself Autopilot More than 400 tests on real clusters per release, including every supported upgrade path²⁰
Node repair	Rancher Auto Replace on node-driver machine pools once you set a timeout; custom and bare-metal nodes are yours¹²²³	Syself Autopilot Cloud nodes rebooted, then replaced if they don’t recover; bare-metal nodes rebooted, and Syself tells you what broke when the hardware is at fault⁴
Recovering a lost cluster	Rancher Restored from RKE2’s scheduled etcd snapshots, kept by default on each server’s own disk¹⁴	Syself Autopilot Recreated from its Cluster object and your manifests in Git; no etcd backup needed. Data comes back from your own backups⁸
Security evidence	Rancher RKE2 passes most CIS controls by default and has a DISA STIG; Rancher scans clusters against CIS profiles and lists what to fix¹¹³⁵³⁶	Syself Autopilot CIS and STIG conformance; an SBOM and advisories with every release, in the Version Hub²²²¹
Support	Rancher Community, or 24x7 with Rancher Prime¹⁸	Syself Autopilot Support from the Syself team on business days included with Syself Autopilot; Premium Support with a custom SLA and 24/7 cover; migration by Syself or agencies¹⁰³³
Price	Rancher Free and open source; Rancher Prime priced on request¹⁸	Syself Autopilot A platform fee plus a usage-based fee tied to your infrastructure spend, not to nodes or clusters; request a 14-day trial without limits or a free plan for one cluster of up to 5 nodes of any size¹⁰

Rancher’s editions change often; check suse.com for the current Rancher Prime offer.

Who Does the Work of Running Kubernetes

Every Kubernetes setup needs the same work under it. With Rancher the software is free, and every job below stays with you, fully or in part.

self-run

6 of 13 jobs left to you, 7 shared

fully managed, on your servers

0 of 13 jobs left to you, 5 shared

Each segment is one job. Point at it to see which job it is, or click it to read why.

Left to you Shared Handled by the vendor, or not needed

Servers Create, provision and replace the machines
Create and set up new Hetzner Cloud servers Rancher creates them through a community driver you keep working.¹⁵ Syself builds each node in the rescue system: image, config and control-plane images are on disk before first boot, so it needs no internet or registry.¹⁹

Rancher Shared
Syself Autopilot Syself
Bring bare-metal servers into a cluster Hetzner has no server types or instant delivery for bare metal, so renting is the only manual step. Syself checks the disks, installs Syself Linux and joins the server. With Rancher you install Linux and run the registration command yourself.⁹¹⁵

Rancher You
Syself Autopilot Syself
Replace a Hetzner Cloud server that fails Rancher’s Auto Replace works on machine pools you enable it for; Syself Autopilot does it by default.¹²⁴

Rancher Shared
Syself Autopilot Syself
Handle a failing bare-metal server Syself reboots the node and, when the hardware is at fault, tells you what broke so you can open the Hetzner ticket. Hetzner has no API for tickets, so that step stays with you. Rancher leaves custom nodes to you.⁴

Rancher You
Syself Autopilot Shared
Operating system Install it, patch it and keep every node the same
Patch the operating system and follow its CVEs Syself ships each fix in a new Syself Linux image; 1.36 v7, for example, updated the kernel and ten OS packages.³³¹ With Rancher the host OS and its CVEs are yours, unless you run SL Micro.¹⁷

Rancher You
Syself Autopilot Syself
Keep every node the same Syself Linux is read-only and replaced rather than patched, so nodes don’t drift. Hand-patched nodes drift; Elemental is SUSE’s image-based OS you run.³¹⁷

Rancher You
Syself Autopilot Syself
Kubernetes Install, configure and upgrade the components
Decide when to upgrade Neither upgrades on its own. Syself ships tested updates every week, and the Version Hub shows what changed, what got fixed and where security stands; you choose when each cluster moves.²³⁷

Rancher You
Syself Autopilot Shared
Upgrade Kubernetes without breaking workloads Kubernetes ships a patch release about monthly; minors go one at a time.³⁸³⁹ Rancher rolls the nodes, but the host OS and Hetzner integrations are yours.¹³ On Syself Autopilot, you trigger one update and it moves the OS, Kubernetes and in-cluster components together.²⁵

Rancher Shared
Syself Autopilot Syself
Test each platform update before it reaches your clusters SUSE tests RKE2; the Hetzner driver, integrations and your settings are yours to test.³⁴ Only Syself releases that pass on real clusters become available.²⁰

Rancher Shared
Syself Autopilot Syself
Inside the cluster The network plugin, the Hetzner integration and storage
Install and upgrade the Hetzner integration and storage A Cluster Stack pins the network plugin, Hetzner integrations and storage, and moves them together.² RKE2 ships its own network plugin,³² but the Hetzner cloud controller and storage driver are yours to install and upgrade.²⁷

Rancher Shared
Syself Autopilot Syself
Day to day Backups, access, logs and the workloads
Recover a lost cluster RKE2 snapshots etcd to each server’s disk by default; copying them off is yours.¹⁴ Syself recreates a lost cluster from its Cluster object and your manifests in Git, so there is no etcd snapshot to restore; Secrets you never committed go in a Velero backup.⁸

Rancher Shared
Syself Autopilot Shared
Run databases and services, and back up their data Syself ships the storage and documents operators such as CloudNativePG, with point-in-time restore.²⁵ You run the databases, or an agency runs them for you in your cluster.³³ The same holds with Rancher.

Rancher You
Syself Autopilot Shared
Lock down access, networking and logs Rancher signs users in to all clusters via your identity provider and manages roles centrally.⁴⁰ Syself hardens the API server, can limit it to trusted IPs and supports OIDC.²²²⁸²⁹ RBAC, SSH, network policies, logs and metrics stay yours.⁷⁴¹

Rancher Shared
Syself Autopilot Shared

On every option, Syself Autopilot included, you still back up workloads and data, run monitoring and alerting, and set access, encryption and network policies. See what you own and what Syself manages.

What Each One Costs

The Hetzner server bill is the same either way. With Rancher the software is free and the work is yours. With Syself Autopilot, the fee pays Syself to do it.

self-run

License, open source: €0
Rancher Prime support subscription: On request

fully managed, on your servers

What Syself runs for you

Servers, OS, Kubernetes and cluster components
Releases tested on real clusters, with SBOM and VEX
Support from the Syself team

Platform fee Usage-based fee

Usage-based fee tied to your infrastructure spend, not to nodes or clusters.

Estimate your price or tell us about your setup for a tailored price

Request a 14-day trial without limits or a free plan for one cluster of up to 5 nodes of any size, no vCPU cap, bare metal included.

Your servers Billed separately by your cloud or bare-metal provider

Syself Autopilot charges a platform fee plus a usage-based fee tied to your infrastructure spend.¹⁰ SUSE prices Rancher Prime on request.¹⁸

Syself Autopilot was the ideal solution for us. We wanted the raw computing power of Hetzner dedicated servers but without the added complexities such as maintaining a hardened OS image. All the best practices seem to be implemented and the support has been very helpful and professional.

Stephen Hoogendijk

CTO, Maxroll Technologies B.V.

Questions Teams Ask Before Switching

Short answers, each linked to Syself’s and SUSE’s documentation.

: For Kubernetes on Hetzner, yes. Rancher is a console for clusters on many providers, and you run Rancher and the clusters.²³ Syself Autopilot is a managed service in which Syself does the platform work on Hetzner Cloud and bare metal.¹
: Rancher can manage any conformant cluster, including one on Hetzner. It has no built-in Hetzner node driver, so Hetzner Cloud machines need a community driver, and bare-metal servers join as custom nodes you set up yourself.¹⁵
: Yes. A bare-metal server includes its NVMe disks, and traffic on the default 1 Gbit uplink is unlimited.²⁴ Databases run on those disks under an operator such as CloudNativePG,²⁵ and KubeVirt runs virtual machines on the same servers.²⁶ You run the databases, or an agency runs them for you in your cluster.
: Syself Autopilot first handles node failures itself: it reboots a failed Hetzner Cloud node, replaces it if it doesn’t recover, and on bare metal tells you what broke when the hardware is at fault.⁴ Syself Autopilot includes support from the Syself team on business days; Premium Support adds a custom SLA and 24/7 cover.¹⁰³⁰ With self-hosted Rancher you are on call, and Rancher Prime adds 24x7 support from SUSE.¹⁸
: RKE2 has CIS-hardened defaults and a DISA STIG; Rancher scans against CIS.¹¹³⁵³⁶ Patching stays with you: tracking CVEs, testing fixes and rolling them out to every node, at least monthly.¹⁷³⁸ Syself checks each CVE against each release’s SBOM and ships fixes in a release built and tested as one; one with an overdue CVE does not ship.³⁰³⁷ Syself Linux is read-only, and nodes need no private network.³²²⁴²
: On both, you decide when. Rancher rolls the nodes to the version you pick, and restoring an etcd snapshot rolls it back.¹³¹⁴ Syself ships tested updates every week; you trigger one and Syself replaces nodes one at a time. There is no rollback, so a stalled upgrade is fixed forward.²⁶
: With Rancher you still run the Rancher server, patch the node OS, set up Hetzner servers and upgrade the Hetzner integrations.¹⁶¹⁷¹⁵²⁷ Syself does that work for a platform fee plus a usage-based fee tied to your infrastructure spend, not to nodes or clusters.⁴³¹⁰ Try the pricing calculator.
: Your workloads and data, backups, GitOps, etcd encryption, OIDC and RBAC, SSH lockdown, network policies, logs and metrics.⁷⁸⁴¹ The shared-responsibility page lists every item.
: Your workloads move as to any conformant cluster: manifests, Helm charts and data are standard Kubernetes.¹ Rancher features such as Projects, Fleet bundles and SUSE Security (NeuVector) policies need a replacement.
: Then you compare a distribution you run with a managed service. See Syself Autopilot vs RKE2 and K3s.