Managed Kubernetes
that scales with you
Launch namespaces or dedicated clusters in minutes. We handle updates, scaling, security and backups — so you can focus on your product.
How it works
Choose plan
Namespace or Dedicated Cluster
Connect & deploy
kubectl, Helm or CI/CD
We operate it
Updates, scaling, 24/7 monitoring
Why not just use AWS?
You don't need a cluster. You need a namespace.
AWS EKS charges $73/month just for the control plane — before a single container runs.
Sources
AWS EKS: aws.amazon.com/eks/pricing, as of March 2026. Self-hosted estimates based on a 3-node Hetzner Dedicated setup. Setup times are based on experience.
Our Features
Highly Available Control Plane
Redundant control plane with automatic failover for maximum availability.
Quick Start
Namespaces & clusters ready in minutes.
Auto-Scaling & Self-Healing
Kubernetes automatically handles failures and load spikes.
Security & Backups
Network isolation, compliance clusters & daily backups.
Flexibly Extensible
Storage, databases, backups — all with one click.
Transparent Pricing
Base plan + metered resource allocation. No surprises.
We manage it for you
Upgrades, patches and 24/7 monitoring.
Namespace Pricing
Transparent base price + metered resource allocation.
Namespace PAYG
Billed by CPU & RAM usage while your pods run
- No minimum usage
- Budget alerts & spending notifications
Add-ons Coming soon
Kubernetes logo © The Kubernetes Authors, licensed under CC-BY-4.0
Frequently Asked Questions
What is the difference between a namespace and a cluster?
A namespace is an isolated area within a shared cluster. You get your own CPU, RAM and storage quotas, network policies and RBAC — without managing your own cluster. Ideal for small to medium teams.
How much does managed Kubernetes cost compared to AWS?
AWS EKS charges $73/month just for the control plane — plus compute costs. With ITSH, you start with a PAYG namespace from €3/month base fee, plus usage-based billing for CPU and RAM. That is 60–75% cheaper than comparable AWS setups.
Do I need a DevOps team for Kubernetes?
No. We handle updates, security patches, monitoring and backups. You deploy your apps via kubectl, Helm or CI/CD — we take care of the rest.
How do I migrate my app to Kubernetes?
Containerise your app with a Dockerfile, write a Kubernetes manifest or Helm chart, and deploy it to your namespace. Our support team is happy to help you get started.
Where are the servers located?
All servers are in German data centres. We use Hetzner infrastructure in Falkenstein and Nuremberg. GDPR-compliant, NIS2-ready.
Can I switch from AWS/GCP to ITSH?
Yes. Kubernetes workloads are portable. Export your manifests, adjust your container registry and ingress configuration, and deploy them to your ITSH namespace. We support standard Kubernetes — no vendor lock-in.