Skip to main content

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

Both put the cluster in your own Hetzner account. Edka gives you k3s and an app and database dashboard; you back up before each upgrade and apply add-on updates. Syself Autopilot, run by Syself, keeps the servers, OS, Kubernetes and cluster components current in tested releases.

Edka

What it is
Edka sets up k3s clusters in your own Hetzner account, with a dashboard for apps, databases, AI agents, observability and add-ons on top.192128
Who does the work
Edka Digital S.L., in Barcelona, runs the dashboard; it launched as a public beta in August 2025.1929 You back up before each Kubernetes upgrade, apply add-on updates and secure the cluster after setup.222341
Where it runs
Cloud clusters keep the control plane on Hetzner Cloud servers, and dedicated servers join as workers only.25 A Satellite cluster, in beta, turns one server you own into a single-node k3s cluster that you upgrade yourself.38

What it is
A separate managed Kubernetes service for Hetzner: upstream Kubernetes on Syself Linux, shipped with the in-cluster components as one tested release.123 It replaces failing cloud nodes and tells you what broke when bare-metal hardware fails.4
Who does the work
Syself builds Syself Linux, sets up your cloud and bare-metal servers and upgrades everything in one tested Cluster Stack release.12312 Syself Autopilot includes support from the Syself team.1134
Where it runs
Control plane and workers can run on Hetzner Cloud or bare-metal servers in your own Hetzner account.113

Which One Fits You?

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

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

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

Delivery modelEdka Dashboard that sets up and manages clusters in your Hetzner account; detach it and the cluster keeps running19Syself Autopilot Fully managed Kubernetes run from Syself’s management cluster; if that is unreachable, your cluster keeps running1
KubernetesEdka k3s with embedded etcd; Flannel or Cilium, fixed at creation21Syself Autopilot Upstream Kubernetes in a tested Cluster Stack release that pins the OS, Kubernetes and in-cluster components2
Control planeEdka One or three Hetzner Cloud servers; a dedicated server only as a single-node Satellite cluster, in beta212538Syself Autopilot Hetzner Cloud or bare-metal servers, one or three, in your account13
Bare metalEdka Workers only; Debian 13 written with installimage, RAID 1, 10 to 20 minutes per server; Standard plan and up2520Syself Autopilot Control plane and workers, no vSwitch needed; Syself checks the disks and installs Syself Linux from the rescue system, so the node boots with nothing to download12737
Node OSEdka Debian 13 by default, or Ubuntu 24.04 or 26.04; security updates installed in place daily2122Syself Autopilot Syself Linux: 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 included3
Kubernetes upgradesEdka The dashboard shows the next version; you start the upgrade after taking a backup2322Syself Autopilot Tested updates every week, listed in the Version Hub; you trigger one and Syself drains, removes and replaces each node, with no rollback52
Release testingEdka No test process published22Syself Autopilot More than 400 tests on real clusters, including every supported upgrade path; a cluster can only use a release that passed6
Node repairEdka Warning when nodes are not ready; automatic replacement not described23Syself 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 fault4
Security fixesEdka Nodes install OS security updates daily and can reboot in a maintenance window; a Vulnerabilities tab lists node, Kubernetes and image CVEs3940Syself Autopilot Hardened to the CIS Kubernetes Benchmark; each release ships an SBOM and a VEX verdict per node-image CVE, and a release with an overdue CVE does not ship363534
In-cluster componentsEdka Curated add-ons preconfigured for Hetzner; each update applied separately2723Syself Autopilot Network plugin, Hetzner integration, DNS and storage pinned in the release and upgraded together2
Databases and appsEdka PostgreSQL, MySQL, Valkey and ClickHouse through operators, app deployments and runners in the dashboard2627Syself Autopilot Standard operators; you run them, or an agency runs them for you in your cluster15
Recovering a lost clusterEdka Encrypted etcd snapshots to Edka-managed storage, kept 7, 30 or 90 days by plan24Syself Autopilot Recreated from its Cluster object and your manifests in Git; no etcd backup needed. Data comes back from your own backups10
SupportEdka Email in 2 business days on Standard, email and chat in 8 business hours on Pro, 24/7 on Enterprise; 99.5% uptime SLA on paid plans20Syself 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 agencies1134
PriceEdka Free plan; €80 or €250 a month; Enterprise from €500 a month, plus your Hetzner bill20Syself 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, no vCPU cap, bare metal included11

Edka’s plans and features are changing quickly; check edka.io for the current offer. Syself Linux and bare-metal installs from the rescue system are available from release 1.36.37

Who Does the Work of Running Kubernetes

Every Kubernetes setup on Hetzner has to cover four layers, plus day-to-day operations. See which jobs you keep with each one.

Edka k3s + app platform

4 of 13 jobs left to you, 8 shared

fully managed, on your servers

0 of 13 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 server that fails Syself Autopilot reboots a failing cloud node and replaces it from a fresh image if it doesn’t recover.4 Edka shows a warning; its docs don’t describe automatic replacement.23
    Edka You
    Syself Autopilot Syself
  • Add servers when workloads grow Edka autoscales cloud node pools you enable it on, not bare-metal pools.2225 On Syself Autopilot you change a replica count, or install the Cluster Autoscaler, which then scales through Syself.17
    Edka Edka
    Syself Autopilot Shared
  • Bring a bare-metal server into the cluster Hetzner has no server types or instant delivery for bare metal, so renting is the only manual step. Edka installs Debian 13 and joins it as a worker over a vSwitch.25 Syself builds the node in the rescue system, so it boots with nothing to download, needs no vSwitch and can serve the control plane.123713
    Edka 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.4 Edka’s docs don’t describe what happens when a running server fails.25
    Edka You
    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, never patched, so nodes can’t drift.3 Edka nodes are patched in place by daily security updates.22
    Edka Shared
    Syself Autopilot Syself
  • Know about and patch OS CVEs Syself checks each CVE against the release’s SBOM and ships fixes in a new tested release.83435 Edka installs OS updates daily, lists open CVEs per node and can reboot nodes in a maintenance window.3940
    Edka Shared
    Syself Autopilot Syself
  • Kubernetes Install, configure and upgrade the components
  • Keep Kubernetes and the platform up to date Syself ships tested updates every week and lists each one in the Version Hub: what changed, what got fixed and where security stands. You decide when on both; on Syself you trigger the update, and it drains, removes and replaces each node on its own.5 Edka asks you to back up and check custom resources first.22 Removed-API checks and PodDisruptionBudgets stay yours.6
    Edka Shared
    Syself Autopilot Syself
  • Test each platform update before it ships Syself tests every release on real clusters; it tests its own stack, not your manifests.6 Edka pins the k3s version it validates and publishes no test process for the whole stack.3822
    Edka You
    Syself Autopilot Syself
  • Inside the cluster The network plugin, the Hetzner integration and storage
  • Upgrade the network plugin, Hetzner controller and storage driver together They move with the Cluster Stack on Syself Autopilot.2 On Edka you apply each add-on update yourself.23
    Edka Shared
    Syself Autopilot Syself
  • Run databases inside the cluster Edka installs the operators and gives you a UI; backups go to your bucket.26 Syself ships the storage and documents CloudNativePG.31 You run the databases, or an agency runs them for you in your cluster.1518
    Edka Shared
    Syself Autopilot Shared
  • Day to day Backups, access, logs and the workloads
  • Back up application data Syself documents CloudNativePG with point-in-time restore and Velero for volumes.3110 The data is yours. Edka’s etcd backups don’t include volume data.24
    Edka You
    Syself Autopilot Shared
  • Get help around the clock Edka includes 24/7 support and a custom uptime SLA on Enterprise, from €500 a month.20 Syself Autopilot includes support from the Syself team on business days; Premium Support adds a custom SLA and 24/7 cover.1134
    Edka Shared
    Syself Autopilot Shared
  • Lock down access, networking and logs Edka encrypts Secrets and offers roles, logs, metrics and a Cilium host firewall.213027 Syself runs a host firewall and can limit the API to trusted IPs.373233 RBAC, SSH, etcd encryption, network policies and logs stay yours.93444
    Edka 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

Both run on the same Hetzner servers in your account, so the server bill is the same. Edka charges a plan fee, or none on the free plan. Syself charges a platform fee plus a usage-based fee tied to your infrastructure spend, not to nodes or clusters.

Edka k3s + app platform
Free plan, one non-HA cluster up to 24 vCPUs
€0
a month, Standard: 2 clusters, HA, bare-metal pools
€80
a month, Pro: 4 clusters
€250
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

Edka prices exclude VAT; yearly billing gives two months free, and extra clusters on Standard and Pro cost €60 a month.20

Questions Teams Ask Before Choosing

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

Other Comparisons

Running on Hetzner, or Planning To?

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 before you talk to anyone.

Sources

  1. 1. What is Syself Autopilot?
  2. 2. What is a Cluster Stack?
  3. 3. Syself Linux: an immutable, verifiable node OS
  4. 4. Node health monitoring and self-healing
  5. 5. Syself docs: cluster upgrades
  6. 6. How Syself tests a Cluster Stack release
  7. 7. Fast node provisioning from the rescue system
  8. 8. How Syself builds a secure node OS
  9. 9. Syself docs: ownership and shared responsibility
  10. 10. Syself docs: backup and disaster recovery
  11. 11. Syself pricing and support plans
  12. 12. Syself docs: add bare-metal servers
  13. 13. Syself docs: bare-metal control planes
  14. 14. Syself docs: run virtual machines with KubeVirt
  15. 15. Syself docs: run it yourself, or with help
  16. 16. Syself docs: the economics of owning vs renting
  17. 17. Syself docs: Cluster Autoscaler
  18. 18. Syself for agencies
  19. 19. Edka homepage
  20. 20. Edka pricing
  21. 21. Edka docs: create a cluster
  22. 22. Edka docs: update a cluster
  23. 23. Edka docs: clusters overview
  24. 24. Edka docs: cluster backups and restore
  25. 25. Edka docs: Hetzner Metal server pools
  26. 26. Edka docs: databases overview
  27. 27. Edka developer documentation
  28. 28. Hetzner Community: managed Kubernetes with Edka on Hetzner
  29. 29. Show HN: Edka, Kubernetes clusters on your own Hetzner account
  30. 30. Edka docs: cluster access and security
  31. 31. Syself docs: choose storage
  32. 32. Syself docs: restrict API server access
  33. 33. Syself docs: configure OIDC
  34. 34. Syself docs: support channels and SLAs
  35. 35. Syself docs: security evidence a release produces
  36. 36. Syself docs: meet compliance requirements
  37. 37. Syself docs: zero trust on public networks
  38. 38. Edka docs: Satellite clusters
  39. 39. Edka docs: node OS updates
  40. 40. Edka docs: vulnerabilities
  41. 41. Edka security
  42. 42. Kubernetes release cycle
  43. 43. Syself docs: scan workload images
  44. 44. Syself docs: what ships by default and what you bring