Bookable from 4 Nov · Nodes from €19.02/month – control plane included

Managed Kubernetes: you deploy, we run the cluster.

Kubernetes as a Service from our own data centre in Germany
With our managed container hosting (Container as a Service), you create clusters, scale them and delete them again whenever you like. We take care of operating the control plane, network, storage, backup, monitoring and policies. Your clusters run in our own data centre in Hallstadt near Bamberg and are subject to German law.

Pre-register for 4 Nov See prices

Bookable from 4 November 2026. Arrange your contract with our sales team now.

Managed Kubernetes · New cluster
eu-de · Hallstadt DC
Cluster
prod-k8s-01
Node pools
2 · 6 nodes
Version
k8s 1.33
CP Control plane · highly available
● Active
AS Autoscaling · pool “general” 2 → 8
● Enabled
LB LoadBalancer · public IP assigned
● Ready
KY Kyverno · Pod Security Standards
● Enabled
Cluster provisionedManaged Kubernetes · 4 min 12 s
  • Clusters ready in minutes
  • Dedicated, isolated network for every cluster
  • Autoscaling per node pool within limits you set
  • Hourly billing
Why Managed Kubernetes

Managed Kubernetes: the biggest costs come from operations, not from the nodes

The nodes themselves are usually the smaller cost item. Ongoing operations take more effort: the control plane has to be patched, every upgrade tested in advance, and ingress and certificates maintained. On top of that come reliable monitoring and on-call cover outside business hours. We take care of these tasks.

Less operational effort

We take care of running the control plane, Kubernetes upgrades and security patches. Your team concentrates on developing applications instead of maintaining clusters.

Predictable total costs

There is no surcharge for the standard control plane, and no setup fee either. We bill nodes by the hour and persistent volumes by usage.

Secure from day one

Every cluster gets its own network, and backups are retained for 30 days. On request, centron enforces the Pod Security Standards and best practices with Kyverno. You do not need a separate project for security policies.

Looked after by real experts

The experts in our Kubernetes team manage your clusters. And of course our support team, with extensive Kubernetes know-how, is there to help with any questions.

Division of tasks

Run it yourself or Managed Kubernetes? Who does what

The overview shows which tasks lie with your team when you run Kubernetes yourself, and which ones centron takes on in managed operation.

TaskSelf-operatedWith centron
Running and patching the control planeYour own team, around the clockcentron · included
Kubernetes upgradesTest and roll out manuallyAutomatically in the maintenance window on request
CNI, ingress, cert-managerChoose and maintain yourselfCNI and cert-manager preinstalled, ingress available as an add-on
Monitoring and loggingYour own stack, your own maintenanceIncluded as standard
Pod security and policiesBuild your own rule setOn request, centron enforces the Pod Security Standards and best practices with Kyverno
Backup and restoreYour own solution, your own testsCluster backup with 30-day retention included, Velero optional
Network isolation and LoadBalancerManual configurationDedicated network, public IP assigned automatically
How to get started

Your Kubernetes cluster in three steps

Create a cluster

Choose one of three current Kubernetes versions and decide whether the control plane should be highly available. You set the address ranges for the node, pod and service networks yourself.

Put together node pools

Put together your node pools from the offerings C1 to C8, exactly as your workloads require. For each pool you can enable autoscaling and set a lower and an upper limit. CNI, storage provider and cert-manager are already preinstalled.

Deploy

Download the kubeconfig and roll out your applications. Services of type LoadBalancer automatically receive a public IP address. Monitoring and logging are already active at this point.

Scope of services

Kubernetes as a Service: centron provides everything a cluster needs in operation

You choose the node pools and version. We set up network, storage, backup, monitoring, logging and policies and take care of ongoing operations.

Architecture diagram of centron Managed Kubernetes: internet and load balancer in front of the Kubernetes cluster with control plane, version and three node pools (General Purpose, Compute, Application), on the right the centron managed services Platform Observability, Backup & Restore, Security Standards and Ingress, below the infrastructure of compute, network and storage

Clusters and node pools

Clusters can be created, scaled and deleted again within minutes. You put together your node pools from a catalogue of differently sized offerings.

Control plane and versions

The standard control plane is included; the high-availability control plane can be booked as an add-on. Three current Kubernetes versions are available, and new minor versions follow shortly after the upstream release. On request, we carry out patch and minor upgrades automatically in the maintenance window.

Isolated network per cluster

Every cluster gets its own network with source NAT that is not shared with other customers. You can adjust node, pod and service networks individually; the CNI is preinstalled.

Storage and backup

The storage provider is preinstalled and supports volume expansion; persistent volumes are billed pay-per-use. Cluster backups run by default with a 30-day retention period. Velero for the persistent volumes can be enabled at deployment; we bill the S3 storage it uses by consumption.

Monitoring, logging, policies

Monitoring and logging are active from the start. On request, centron enforces the Pod Security Standards and best practices with Kyverno, without you having to write your own rule set.

Ingress and LoadBalancer

cert-manager is always included; you add the ingress controller when you need it. Services of type LoadBalancer receive their public IP address without manual configuration.

Autoscaling per node pool

Each node pool scales independently between a lower and an upper limit that you set. When the load rises, the pool adds nodes automatically. When it falls again, surplus nodes are removed. Because billing is by the hour, you only pay for the nodes that actually ran.

Pool “general”
2 → 8 nodes*
Autoscaling enabled
* Example

Look it up in the glossary: Control plane · Persistent volume

Before you decide

Five questions that settle your configuration

Answer the following questions for your project. For each question you can see which configuration follows from it.

Do production and test run in the same environment?

Then we recommend splitting them into separate clusters rather than namespaces. That way you do not have to draw permissions and network boundaries inside a running cluster. The second cluster only costs the hours in which it runs.

Are your load peaks predictable?

If so, fixed node pools are enough, and the monthly price is known in advance. If not, enable autoscaling and set an upper limit: as the load rises, nodes are added and then removed again automatically.

Do you run applications that must not fail?

Then we recommend the high-availability control plane for €34.95 per month per cluster. For test and CI clusters, the standard control plane, included at no extra cost, is sufficient.

Do your applications store data permanently?

Stateless services do not need their own storage. As soon as databases or uploads come into play, you need persistent volumes: billed pay-per-use, backed up with Velero on request, with the S3 storage for this billed by usage.

Are there requirements on data location?

If so, you need reliable evidence, not just promises. The following are available for your outsourcing file: Hallstadt data centre, ISO 27001 on the basis of IT-Grundschutz and BSI C5:2020 Type 1 attestation for the data centre and cloud platform, and an operator without a foreign parent company.

Work out prices Compare providers How centron safeguards data sovereignty Talk to sales
Use cases

Managed Kubernetes in practice: three typical use cases

SaaS and microservices

Distribute your services across their own node pools according to their resource needs; autoscaling absorbs load peaks. You can clearly demonstrate Germany as the data location to your own customers.

CI/CD and test environments

You provision test and build environments in minutes and delete them just as quickly after use. With short-lived environments, you only pay for the hours actually used.

Regulated workloads

Isolated networks, Pod Security Standards enforced on request and verifiable backups. Operation takes place in a German data centre. Evidence for your outsourcing documentation is available for the data centre and cloud platform.

Prices

Managed Kubernetes pricing: you pay for the nodes, operations are included

Every offering can be used in any node pool, and billing is by the hour. The standard control plane costs nothing extra.

OfferingvCPURAMSSD€ / month€ / hour
C112 GB50 GB€19.02€0.026
C222 GB60 GB€29.16€0.040
C324 GB80 GB€35.04€0.048
C428 GB100 GB€43.80€0.060
C548 GB160 GB€70.08€0.096
C6416 GB200 GB€87.60€0.120
C7816 GB320 GB€140.16€0.192
C8832 GB400 GB€175.20€0.240

All prices net, plus statutory VAT. The offer is aimed exclusively at businesses. The SSD of the nodes is included in the price. Persistent volumes cost €0.05 per GB per month, outbound traffic €0.005 per GB; inbound traffic is free of charge. As of: 12 October 2026.

High-availability control plane

Can be booked optionally per cluster. The standard control plane remains included at no extra cost.

€34.95/ month · €0.0479 / hWork out your configuration

All plans and quotas in the price list →

Success stories

Customer projects on centron infrastructure

Three companies that run their infrastructure at centron. Each story describes the starting point, the solution and the result.

FOC Solutions and centron logos with an award badge in front of mountain peaks symbolising goals achieved together
Success Story

FOC Solutions

FOC Solutions relies on centron as a dependable hosting partner – with a focus on performance and security.

FOC Solutions in detail
GIS Consult and centron logos with an award badge in front of mountain peaks symbolising goals achieved together
Success Story

GIS Consult

GIS Consult runs future-proof hosting at centron: flexible, cost-efficient and tailored to its needs.

GIS Consult in detail
meinBafög and centron logos with an award badge in front of mountain peaks symbolising goals achieved together
Success Story

meinBafög

meinBafög runs its platform at centron – flexibly scalable and without over-provisioning.

meinBafög in detail

Frequently asked questions about Managed Kubernetes

How much does Kubernetes hosting in Germany cost?

At centron you only pay for the nodes; the standard control plane is included. A cluster of three nodes, each with 2 vCPU and 2 GB RAM, costs €148.03 per month – including the high-availability control plane and 5 TB of outbound traffic (€25.60); the NVMe SSD of the nodes is included in the node price. Inbound traffic is free of charge. Comparable clusters cost €167.34 at IONOS, €198.94 at STACKIT (with 4 GB RAM per node, the cheapest current 2-vCPU type) and €523.55 at AWS EKS. Azure AKS does not allow this node size; the smallest permitted variant costs €852.24. Hetzner does not offer Managed Kubernetes. Our own research based on the providers' public price lists and pricing APIs, as of 12 October 2026.

Where can I find affordable Kubernetes hosting in Germany?

With Kubernetes, affordable rarely means “lowest node price”. Three items decide it, and many providers charge for them separately: control plane, storage and outbound traffic. At centron the standard control plane is free of charge. The NVMe SSD of the nodes is included in the node price. Outbound traffic costs €0.005 per GB, persistent volumes cost €0.05 per GB per month. Nodes start at €19.02 per month. In its Standard tier, Azure AKS additionally charges €0.088 per cluster per hour (€64.24 per month), AWS EKS USD 0.10 per cluster per hour – regardless of how large the cluster is.

What is the best Kubernetes hosting provider in Germany?

That depends on three questions: Is the control plane operated for you, and does it cost extra? Is the data stored in Germany, and is there evidence for it? Are storage and traffic part of the price? centron runs the standard control plane free of charge in its own data centre in Hallstadt, which is certified to ISO 27001 on the basis of IT-Grundschutz. IONOS and STACKIT also host in Germany; Hetzner does not offer Managed Kubernetes.

Which Kubernetes hosting providers in Germany offer a free trial?

centron gives new accounts a €200 starting credit valid for 60 days. Three C1 nodes together cost €57.06 per month. The credit is therefore enough to run a small cluster for the full 60 days. There is no setup fee, billing is by the hour, and clusters can be deleted again at any time.

What Kubernetes hosting options are there for small businesses in Germany?

For small teams, a cluster of two to three nodes is usually enough. At centron this starts with C1, with 1 vCPU and 2 GB RAM for €19.02 per month per node; the standard control plane costs nothing extra. Autoscaling absorbs load peaks without you paying for larger nodes all the time. As your needs grow, individual node pools switch to larger offerings up to C8 – without setting up the cluster again.

What does the control plane cost?

At centron the standard control plane is included in the price. The high-availability control plane costs €34.95 per month or €0.0479 per hour and cluster. IONOS does not charge for the control plane either. In its Standard tier, Azure AKS charges €0.088 per cluster per hour, AWS EKS USD 0.10.

How quickly is a cluster ready?

Provisioning usually takes just a few minutes. You choose the version and node pools; everything else runs automatically. Scaling and deleting are just as fast.

Which Kubernetes versions are available?

Three current Kubernetes versions are available at any time. New minor releases are added shortly after the upstream release. On request, we update patch and minor versions automatically in the maintenance window.

How is the network set up?

Every cluster runs in its own isolated network with source NAT that is not shared with other customers. You can adjust node, pod and service networks individually; the CNI is preinstalled.

How do backups work?

Cluster backups are active by default and retained for 30 days. For persistent volumes, you can additionally enable Velero at deployment. Velero is not included in the price: we bill the S3 storage it uses by consumption. The preinstalled storage provider supports volume expansion and is billed pay-per-use.

What is the availability?

The worker nodes are covered by the ccloud³ Compute Engine SLA of 99.5%. The binding value is the one in the service description of the ccloud³ Compute Engine (in German).

Is there a lock-in?

No. centron uses upstream Kubernetes with standard interfaces. Your manifests, Helm charts and GitOps pipelines keep working unchanged, even with another provider.
Read next

centron tutorials: run clusters and compare providers

There are matching guides for every cluster. The kubectl tutorial shows installation and the most important commands, the Docker tutorial how to safely clean up old containers and volumes. The provider comparison puts centron next to other Kubernetes providers in Germany and names the source and date of every figure. All guides can be read without an account.

Cluster basics
Containers & environment
Provider comparison

You create the cluster, we take care of operations.

Nodes from €19.02/month · control plane included

Bookable from 4 November 2026. Arrange your contract with our sales team now.

What does centron Managed Kubernetes offer?

centron operates Managed Kubernetes in its own data centre in Hallstadt near Bamberg. Nodes come in eight sizes from C1 to C8, from €19.02 per month, billed by the hour. The standard control plane costs nothing extra; the high-availability control plane costs €34.95 per month or €0.0479 per hour and cluster. Every cluster runs in its own isolated network with source NAT. Cluster backups run by default with a 30-day retention period; Velero for persistent volumes can be enabled at deployment (S3 storage billed by usage). Monitoring and logging are included. On request, centron enforces the Pod Security Standards and best practices with Kyverno. The worker nodes are covered by the SLA of the ccloud³ Compute Engine of 99.5%. centron's data centre and its ccloud³ cloud platform are certified to ISO 27001 on the basis of IT-Grundschutz and hold a BSI C5:2020 Type 1 attestation. New accounts receive a €200 starting credit. As of: 12 October 2026.