Skip to main content

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

KubeAid is free to run yourself and has a large app catalog. Self-hosted, you patch the Ubuntu nodes, track CVEs and run upgrades; Obmondo does parts of that per server.181011 Syself Autopilot sets up your Hetzner servers, patches the OS and tests each release.173016

Obmondo KubeAid

What it is
KubeAid is an AGPLv3 Kubernetes platform kept in Git and applied by Argo CD, with more than 100 maintained Helm charts, from Cilium and monitoring to database operators.12
Who does the work
You can run it yourself for free, or pay Obmondo per server to watch the clusters, answer alerts and patch them.210 If you host it yourself, you patch the Ubuntu nodes, apply the weekly chart updates and run each upgrade.81
Where it runs
It builds clusters with Cluster API on AWS, Azure and Hetzner Cloud, bare metal and hybrid, and uses CAPH, the Cluster API provider for Hetzner, there.35

What it is
Syself Autopilot is fully managed Kubernetes on your own Hetzner servers, with standard upstream Kubernetes for your apps.13 Syself builds the node OS, the provisioner, KubeGate and the node-repair agent, and tests them together on real clusters before each release.1517281816
Who does the work
Syself runs the management cluster, sets up each server and patches the node OS.1730 Every fix comes as a tested Cluster Stack release that you roll out when you choose. Syself Autopilot includes support from the Syself team.25
Where it runs
It provisions Hetzner Cloud and bare-metal servers in your own Hetzner account, so the servers and the data stay yours.13

Which One Fits You?

Tick what applies. The reasons to choose KubeAid are on this list too.

What applies to you?
Obmondo KubeAid · 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 Obmondo KubeAid at a Glance

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

Delivery modelObmondo KubeAid Open-source platform you run yourself, or Obmondo runs it on a per-server subscription2Syself Autopilot Fully managed Kubernetes; Syself runs the management cluster and the cluster lifecycle13
Management clusterObmondo KubeAid A temporary local cluster hands control to the new cluster, which then manages itself6Syself Autopilot Run by Syself, outside your cluster; if it is unreachable, workloads keep running and changes wait until it is back13
Node OSObmondo KubeAid Ubuntu 26.04 by default, prepared at boot with cloud-init commands87Syself Autopilot Syself Linux from release 1.36 (1.35 runs Ubuntu), read-only and installed from the Hetzner rescue system, so boot needs no internet or registry. A security team tracks each CVE, checks whether your clusters are exposed and ships the fix in a tested release; support is included1517
Security and CVE fixesObmondo KubeAid Weekly chart and security updates; no CVE patch deadlines in its public docs132Syself Autopilot Control plane and kubelet hardened to the CIS Kubernetes Benchmark; an SBOM and VEX verdicts per release, and a release with an overdue CVE does not ship213031
Kubernetes upgradesObmondo KubeAid Change the version in Git; the CLI’s upgrade and restore-from-backup for Hetzner are marked work in progress56Syself Autopilot Tested updates every week, listed in the Version Hub; you trigger one and Syself drains, removes and replaces each node, with no rollback1420
Node repairObmondo KubeAid Cluster API health checks replace control-plane machines and Hetzner Cloud workers that stay not ready for 3 minutes; no check for bare-metal workers33Syself 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 fault18
In-cluster componentsObmondo KubeAid Cilium, Argo CD, Sealed Secrets and monitoring in every cluster, plus 100+ charts updated weekly1Syself Autopilot Network plugin, Hetzner integrations, DNS and storage pinned and tested together in each release14
BackupsObmondo KubeAid Velero on a schedule; whole-cluster recovery needs extra tooling2Syself Autopilot Data backups are yours, with Velero and database operators; a lost cluster is recreated from its Cluster object and your manifests in Git, so no etcd backup is needed22
SupportObmondo KubeAid Community, or from 1 business day to 1 hour response; 24x7 on Gold and Platinum10Syself 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 agencies2527
PriceObmondo KubeAid Free self-hosted; managed from €29 to €265 per server a month10Syself 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 size25

KubeAid’s feature status changes often; check the KubeAid CLI support table. Obmondo prices are per server per month, before volume discounts.

Who Does the Work of Running Kubernetes

For KubeAid, “vendor” means its charts or Obmondo on a subscription. On Syself Autopilot, metrics, alerting, backups, OIDC, RBAC and logs stay with you.212241

Obmondo KubeAid open source + service

1 of 16 jobs left to you, 11 shared

fully managed, on your servers

2 of 16 jobs left to you, 6 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
  • Replace a cloud server that fails Syself Autopilot reboots a failing Hetzner Cloud node and replaces it if it doesn’t recover.18 KubeAid’s Hetzner chart replaces a cloud machine not ready for 3 minutes, and Obmondo answers the alert on a subscription.3310
    Obmondo KubeAid Obmondo
    Syself Autopilot Syself
  • Bring a bare-metal server into a cluster Hetzner has no server types or instant delivery for bare metal, so renting is the only manual step. KubeAid installs Ubuntu with CAPH and installimage.7 Syself Autopilot checks the disks, writes the sealed Syself Linux image and stops a build that fails a check.1719
    Obmondo KubeAid 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.18 With KubeAid, Obmondo’s managed plans include alert handling and incident response.11
    Obmondo KubeAid Shared
    Syself Autopilot Shared
  • Operating system Install it, patch it and keep every node the same
  • Keep every node identical Syself Linux is read-only and replaced as a whole.15 KubeAid builds each node from the same Ubuntu image and boot commands, but finding a change made on a running node is yours.7
    Obmondo KubeAid Shared
    Syself Autopilot Syself
  • Know about and patch OS CVEs Syself checks each CVE against the SBOM and ships fixes in a release built and tested as one; a release with an overdue CVE does not ship.30 Self-hosted KubeAid leaves triage and patching to you; Obmondo’s plans patch in service windows.3211
    Obmondo KubeAid Shared
    Syself Autopilot Syself
  • Kubernetes Install, configure and upgrade the components
  • Decide when to upgrade Neither moves a cluster to a new version on its own.1 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.1431
    Obmondo KubeAid You
    Syself Autopilot Shared
  • Roll every node to the new version Kubernetes patches only its three newest minor versions, and clusters move one minor at a time.4243 Once you trigger it, Syself drains, removes and replaces each node on its own.14 KubeAid’s rolling upgrade is work in progress on Hetzner.65 PodDisruptionBudgets are yours.16
    Obmondo KubeAid Shared
    Syself Autopilot Syself
  • Replace a control-plane node Syself provisions and heals the control plane on your servers.13 KubeAid’s Hetzner chart replaces a control-plane machine not ready for 3 minutes; its whole-cluster restore from backup is marked work in progress.3356
    Obmondo KubeAid Shared
    Syself Autopilot Syself
  • Test each platform update before it ships Syself tests the node OS, Kubernetes and cluster components together on real clusters.16 KubeAid’s CI checks its charts without building a cluster.38
    Obmondo KubeAid Shared
    Syself Autopilot Syself
  • Inside the cluster The network plugin, the Hetzner integration and storage
  • Upgrade the network plugin, Hetzner controller and storage driver together A Cluster Stack moves them as one tested version.14 KubeAid ships weekly chart updates that you pull into your Git repository and apply when you choose.1
    Obmondo KubeAid Shared
    Syself Autopilot Syself
  • Run databases and message queues inside the cluster KubeAid includes the operators.1 Syself Autopilot ships the storage and documents operators such as CloudNativePG.23 You run the databases, or an agency runs them for you in your cluster.27
    Obmondo KubeAid Obmondo
    Syself Autopilot Shared
  • Run GitOps tooling Argo CD comes with every KubeAid cluster; on Syself Autopilot you install Argo CD or Flux.126
    Obmondo KubeAid Obmondo
    Syself Autopilot You
  • Day to day Backups, access, logs and the workloads
  • Answer alerts at night and on weekends Obmondo’s Gold and Platinum plans cover 24x7.10 Syself Autopilot includes support from the Syself team on business days; Premium Support adds a custom SLA and 24/7 cover.25
    Obmondo KubeAid Obmondo
    Syself Autopilot Shared
  • Back up volumes and cluster state KubeAid includes Velero on a schedule.2 Syself recreates a lost cluster from its Cluster object and your manifests in Git, so there is no etcd snapshot to restore. Volume data is yours to back up, for example with Velero.22
    Obmondo KubeAid Shared
    Syself Autopilot Shared
  • Lock down access, networking and logs KubeAid ships an opt-in default-deny namespace policy, a bare-metal host firewall, NetBird and Keycloak.32 Syself nodes check certificates behind a default-deny firewall.39 You can limit API access and add OIDC.2829
    Obmondo KubeAid Shared
    Syself Autopilot Shared
  • Store metrics, build dashboards and route alerts KubeAid installs a monitoring stack, and Obmondo’s plans watch the alerts.111 Syself repairs failing nodes but ships no metrics store, dashboards or alert routing for your apps.1841
    Obmondo KubeAid Shared
    Syself Autopilot You

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 server bill is the same. Self-hosted KubeAid is free, and running it is your work.40 Obmondo charges per server for operations.1110 Syself Autopilot charges a platform fee and a usage-based fee tied to your infrastructure spend.25

Obmondo KubeAid open source + service
Self-hosted, open source
€0
Per server a month, monitoring and alerts
€29
Per server a month, business-hours plans
€129–€165
Per server a month, 24x7 plans
€199–€265
Per hour of consulting, after the free hours in your plan
From €49
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.

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

Obmondo’s volume discounts show only in its calculator. Consulting beyond your plan’s free hours is billed per minute, €198 an hour outside business hours.10 Migration has no published price.11

Questions Teams Ask Before Choosing

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

Other Comparisons

Running Kubernetes on Hetzner?

Request a 14-day trial without limits on your own Hetzner account or a free plan for one cluster of up to 5 nodes of any size. You can price your servers in the pricing calculator first.

Sources

  1. 1. KubeAid on GitHub
  2. 2. KubeAid website
  3. 3. KubeAid docs: getting started
  4. 4. KubeAid docs: why KubeAid
  5. 5. KubeAid CLI on GitHub (support table)
  6. 6. KubeAid CLI: architecture
  7. 7. KubeAid CLI: bare-metal provisioning
  8. 8. KubeAid CLI: config reference
  9. 9. KubeAid CLI: Kubernetes version support
  10. 10. Obmondo pricing
  11. 11. Obmondo
  12. 12. CAPH pull request sponsored by Obmondo
  13. 13. What is Syself Autopilot?
  14. 14. What is a Cluster Stack?
  15. 15. Syself Linux: an immutable, verifiable node OS
  16. 16. How Syself tests a Cluster Stack release
  17. 17. Fast node provisioning from the rescue system
  18. 18. Node health monitoring and self-healing
  19. 19. Syself docs: adding bare-metal servers
  20. 20. Syself docs: maintenance prechecks and no rollback
  21. 21. Syself docs: ownership and shared responsibility
  22. 22. Syself docs: backup and disaster recovery
  23. 23. Syself docs: choose storage
  24. 24. Syself docs: run virtual machines with KubeVirt
  25. 25. Syself pricing and support plans
  26. 26. Syself docs: GitOps overview
  27. 27. Syself for agencies and integrators
  28. 28. Syself docs: restrict API server access
  29. 29. Syself docs: configure OIDC
  30. 30. Syself docs: support channels and CVE patch windows
  31. 31. Syself docs: security evidence per release
  32. 32. KubeAid security
  33. 33. KubeAid: Hetzner MachineHealthCheck template
  34. 34. Syself docs: run it yourself or with help
  35. 35. Syself docs: run the CIS benchmark with kube-bench
  36. 36. Syself docs: scan workload images
  37. 37. Syself docs: mix cloud and bare-metal pools
  38. 38. KubeAid CI workflows
  39. 39. Syself docs: zero trust on public networks
  40. 40. Syself docs: the costs of owning servers
  41. 41. Syself docs: what observability ships and what you bring
  42. 42. Kubernetes releases and support period
  43. 43. Kubernetes version skew policy