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.
What you get with Syself Autopilot
Tick what applies. The answer includes the needs where Edka is the better choice.
The answer updates as you go. Every need on the list counts, including the ones that point away from us.
One short fact per side for each theme, each linked to its source.
| Theme | fully managed, on your servers | |
|---|---|---|
| Delivery model | Edka Dashboard that sets up and manages clusters in your Hetzner account; detach it and the cluster keeps running19 | Syself Autopilot Fully managed Kubernetes run from Syself’s management cluster; if that is unreachable, your cluster keeps running1 |
| Kubernetes | Edka k3s with embedded etcd; Flannel or Cilium, fixed at creation21 | Syself Autopilot Upstream Kubernetes in a tested Cluster Stack release that pins the OS, Kubernetes and in-cluster components2 |
| Control plane | Edka One or three Hetzner Cloud servers; a dedicated server only as a single-node Satellite cluster, in beta212538 | Syself Autopilot Hetzner Cloud or bare-metal servers, one or three, in your account13 |
| Bare metal | Edka Workers only; Debian 13 written with installimage, RAID 1, 10 to 20 minutes per server; Standard plan and up2520 | Syself 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 OS | Edka Debian 13 by default, or Ubuntu 24.04 or 26.04; security updates installed in place daily2122 | Syself 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 upgrades | Edka The dashboard shows the next version; you start the upgrade after taking a backup2322 | Syself 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 testing | Edka No test process published22 | Syself Autopilot More than 400 tests on real clusters, including every supported upgrade path; a cluster can only use a release that passed6 |
| Node repair | Edka Warning when nodes are not ready; automatic replacement not described23 | 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 fault4 |
| Security fixes | Edka Nodes install OS security updates daily and can reboot in a maintenance window; a Vulnerabilities tab lists node, Kubernetes and image CVEs3940 | Syself 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 components | Edka Curated add-ons preconfigured for Hetzner; each update applied separately2723 | Syself Autopilot Network plugin, Hetzner integration, DNS and storage pinned in the release and upgraded together2 |
| Databases and apps | Edka PostgreSQL, MySQL, Valkey and ClickHouse through operators, app deployments and runners in the dashboard2627 | Syself Autopilot Standard operators; you run them, or an agency runs them for you in your cluster15 |
| Recovering a lost cluster | Edka Encrypted etcd snapshots to Edka-managed storage, kept 7, 30 or 90 days by plan24 | Syself Autopilot Recreated from its Cluster object and your manifests in Git; no etcd backup needed. Data comes back from your own backups10 |
| Support | Edka 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 plans20 | 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 agencies1134 |
| Price | Edka Free plan; €80 or €250 a month; Enterprise from €500 a month, plus your Hetzner bill20 | 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, 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
Every Kubernetes setup on Hetzner has to cover four layers, plus day-to-day operations. See which jobs you keep with each one.
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.
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.
What Syself runs for you
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.
Edka prices exclude VAT; yearly billing gives two months free, and extra clusters on Standard and Pro cost €60 a month.20
Short answers, each linked to Edka’s and Syself’s documentation.
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.