Kubernetes without an ops team – we run it for you.

What managed Kubernetes means for you

Maybe your software vendor said the new version "only runs on Kubernetes now". Maybe your own application is outgrowing a single server. Either way, companies without an IT department face the same question: who looks after it? Managed Kubernetes is our answer for exactly this situation. You get a modern, resilient platform without anyone in your company having to learn how it works.

Kubernetes itself isn't rocket science, but it has a lot of knobs. Set up wrongly, it costs too much, is insecure or fails at the worst moment. Set up properly, you mostly notice one thing: that your software runs.

Who does what

With managed Kubernetes, three parties share the work. The cloud provider runs the data centres and the cluster's control plane, the part that decides which application runs on which server. We take care of everything above that: setup, security, updates, monitoring, backups and moving your applications over. You tell us what your software needs, approve bigger changes and are reachable when we need a decision.

We write this split down in a short operations handbook. In plain language, it says how the cluster is built, who has access to what and what happens in an emergency. That way you don't depend on our memory.

How an update works

Kubernetes releases several versions a year, and older versions eventually stop getting security updates. Whoever postpones updates ends up facing one big, risky jump. So we keep your cluster up to date in small steps. Before every update we check whether your applications use features that disappear in the new version, and we apply the update to a test environment first.

In production we replace the servers one after another. Your applications move to the servers that are already updated while the others keep running. For you, at best, that means a short email saying the update is done – and nothing else.

Data protection and providers in the EU

Your data stays in the EU. We choose the right provider together, based on your requirements for data protection, cost and features. What matters to us is that the choice is reasoned and documented – not that it pleases our favourite provider.

We grant access on the principle of least privilege. Who may do what is written down, and credentials are stored encrypted, not in a spreadsheet.

When something happens at night

A cluster restarts crashed applications by itself and moves them to healthy servers. Many problems are solved like that before anyone notices. For everything else, monitoring runs around the clock: it checks whether your applications are reachable, whether storage is running low and whether certificates are about to expire, and it alerts our team around the clock when something is wrong.

We don't just check that backups exist. We rehearse the restore before you really need it.

No lock-in

Everything we set up lives as code in your repository: the cluster's structure, your applications' configuration, the rules for access and backups. If you later want to build your own team or change provider, someone else can take over seamlessly. We help with the handover instead of making it harder.

How we build and secure clusters in general is explained on the Kubernetes consulting page. Whether managed Kubernetes suits you is best settled in a free first call.