The management cluster is the one piece Syself runs for you. It provisions your workload clusters, keeps them healthy, and rolls out upgrades, and you reach it through its Kubernetes API and the Syself console. Your workload clusters always run on your own Hetzner servers. This page covers where the management cluster itself runs.

Syself hosts it by default#

By default your organization receives its own namespace on a management cluster that Syself hosts and operates. You sign in through Syself's identity management, declare your clusters, and there is nothing to run or patch on the management side. This is the right choice for most teams.

Or run it in your own account#

You can also run the management cluster in your own Hetzner account. Syself still operates it, the same way it operates your workload clusters: it builds the cluster, keeps it healthy, and upgrades it. The difference is where it runs, not who keeps it running.

This is the arrangement you already have for your workload clusters, your servers and your account with Syself managing them, now covering the management cluster too. The control plane, its keys, and its audit trail sit inside your own account and identity management, which is what a regulated or sovereignty-sensitive environment needs. It also adds cost and setup, so it is worthwhile when that requirement is real. To inquire, email the Syself sales team at contact@syself.com⁠.

Run a dedicated management cluster in your own account covers what moving it in changes and when to choose it. Sovereignty and data residency puts it in the wider picture.