Where Managed Kubernetes fits

Teams running Kubernetes in Switzerland choose between four layers of the market. Each makes a different trade-off between control, operational burden, and cost. This page maps those layers so you can see where VSHN Managed Kubernetes sits, and why we built it for the gap in the middle.

The four layers

Do-it-yourself Kubernetes

Self-managed Kubernetes gives you total control: you pick every component, set your own upgrade cadence, and run on any infrastructure. That control is also the cost. Running Kubernetes in production means owning the node lifecycle, version upgrades every few months, CNI and ingress decisions, storage operations, security patching, and the on-call rotation behind all of it.

Consider DIY when: you have a mature platform engineering team that treats Kubernetes operations as a core competency, and you need control over every layer.

CSP managed control planes

Managed Kubernetes engines from a cloud service provider or managed service provider (Exoscale SKS, STACKIT, IONOS, OVHcloud and similar) operate the API server and etcd for you. This is genuinely useful, but the name oversells it. Node lifecycle, version upgrades of your workloads' dependencies, ingress, storage, observability, and add-on compatibility remain your job. A managed control plane is not a managed platform.

Consider a CSP control plane when: you want someone else to run the control plane but your team is ready and willing to operate everything above it.

VSHN Managed Kubernetes (the missing middle)

This service takes ownership of the whole platform lifecycle on one opinionated, standardized stack: Talos as the immutable OS, Cilium for networking, the Gateway API for ingress, Rook / Ceph for storage, all driven by Cluster API. VSHN runs version upgrades, OS updates, and the core components on a defined maintenance schedule. You get Kubernetes as a first-class interface with the operational weight lifted, without paying for enterprise scope you do not need.

It is deliberately bounded: standardized configurations, business-hours operations, and a clear responsibility line. That is what keeps it simpler and lower cost than an enterprise platform.

Consider VSHN Managed Kubernetes when: you want production Kubernetes operated for you, you value Swiss sovereignty, and an enterprise platform like OpenShift is more than your workloads require.

Enterprise OpenShift

Managed OpenShift is the enterprise option: continuous operations, higher service levels, integrated developer tooling, and the compliance posture regulated industries need. It is the right tool when your workloads demand around-the-clock operations and regulated-grade guarantees, and more than you need when they do not.

Consider OpenShift when: you operate regulated or business-critical workloads that justify continuous operations and a broader enterprise feature set. See Managed OpenShift.

Which layer is right for you?

If you want the cluster genuinely run for you but an enterprise platform is overkill, Managed Kubernetes is the layer built for that gap. Register your interest and tell us about your clusters. We will discuss whether the platform fits your team.