Provider and TCO assessment
Compare performance, regions, networking, storage, egress, managed services and operating effort.
Managed Kubernetes
Configure and extend services such as OVHcloud MKS, IONOS Managed Kubernetes or STACKIT SKE for the target workload.
Self-managed & bare metal
Build Kubernetes on cloud VMs, dedicated servers or Proxmox with a reproducible cluster lifecycle.
Networking & private access
Design CNI, network policies, load balancers, Gateway API and administrative access through NetBird together.
GitOps & application platform
Implement registry, secrets, Argo CD or Flux, templates and CI/CD as a repeatable platform baseline.
Managed operations
Operate clusters, add-ons and optionally applications with defined maintenance, backup and response processes.
Kubernetes on German and European infrastructure
WZ-IT evaluates providers, regions, operating models and platform services together. We build and operate Kubernetes on European cloud, bare metal or private cloud and can also take responsibility for applications and delivery processes.
Provider and architecture selection
Sovereignty depends on location, access paths and the operating model
Jurisdiction, data center region, control plane, support access, platform dependencies and ongoing operations must align. We make these criteria explicit before selecting a provider.
Requirements first
Workloads, data classes, availability, scaling, team and budget determine the appropriate infrastructure.
Compare actual provider scope
Hetzner, OVHcloud, IONOS, STACKIT, Open Telekom Cloud and Scaleway differ significantly in managed services and responsibilities.
Define the operating model
A managed control plane, a fully self-operated cluster or a Proxmox private cloud is selected from the target architecture.
Include the application
Containers, databases, deployments and recovery determine whether the platform meets operational requirements.
Service scope
What WZ-IT can own on European infrastructure
We can start with provider selection, implement a defined platform or move an existing cluster into an accountable operating model.
In addition to the cluster, applications need defined processes for delivery, access, observability, recovery and technical ownership.
Delivery
GitOps, CI/CD, separate environments, approvals and reproducible rollbacks.
Network
CNI, network policies, ingress or gateway, DNS, TLS and private access.
Security
OIDC, RBAC, secrets, image validation, policies and traceable changes.
Observability
Metrics, logs, traces, alerting and SLOs for platform and applications.
Backup & restore
Cluster state, persistent data, restore tests and a documented recovery path.
Lifecycle
Updates, CVE assessment, capacity, costs and an agreed operating model.
Selection process
From requirements to a documented provider decision
Selection considers cost, regions, networking, storage, platform services, failure domains and ongoing operating effort and is documented as an architecture decision.
Define constraints
Capture data location, compliance, load, availability and operational ownership.Compare models
Evaluate managed Kubernetes, cloud VMs, bare metal and Proxmox with their responsibilities.Target architecture
Design nodes, networks, storage, load balancing, access and failure domains.Build & migration
Build the platform through automation and migrate applications with test and rollback paths.Operate
Organize monitoring, upgrades, backups, recovery and response with explicit ownership.Starting pointOngoing operations
Three operating models
Comparing three responsibility models
The models mainly differ in who upgrades and supports the control plane, nodes, platform services and applications during normal operations and incidents.
01
Provider-managed
- The provider manages the control plane and, depending on the service, additional components. WZ-IT owns architecture, baseline, add-ons and the agreed workload scope.
For teams that want to outsource control-plane operations
02
WZ-IT managed
- WZ-IT builds the cluster on cloud VMs, bare metal or Proxmox and assumes the agreed technical operating scope.
For infrastructure choice without an internal platform team
03
Co-managed
- Ownership is divided by layer, for example WZ-IT for infrastructure and cluster while the customer team owns deployments and applications.
For internal teams with clearly bounded platform ownership
Sovereignty as a system property
Data center region, platform and operations belong together
The sovereignty assessment covers provider jurisdiction, support access, encryption, technical dependencies and exit paths in addition to the EU region. These criteria are documented for the selected setup.
Define regions and data flows including backup, registry and observability destinations · Document provider, WZ-IT and customer ownership for every platform layer · Support portability through open Kubernetes APIs, IaC, GitOps and tested recovery paths
Frequently asked questions
Clear answers on architecture, delivery, responsibilities and ongoing operations.
- We work with Hetzner, OVHcloud, IONOS, STACKIT, Open Telekom Cloud and Scaleway as well as private or rented bare-metal infrastructure. Selection depends on region, performance profile, managed services, compliance and operating model.
- No. Provider and region are only part of the assessment. Responsibilities, contracts, technical configuration, encryption, access, data flows, backups and the actual processing must also be evaluated.
- Not categorically. Managed Kubernetes reduces control-plane operating effort but ties the platform to specific provider functions and responsibility models. A self-operated cluster offers more control but requires dependable operating processes.
- Yes. We assess cluster resources, data, storage, identities, networking and provider integrations and derive a migration path with tests, data transfer, cutover and rollback.
- Yes. Standard Kubernetes resources are often portable; proprietary load balancers, databases, IAM, storage and observability services require deliberate replacement or remapping.
- If required. Platform and application operations are agreed separately. WZ-IT can containerize, migrate and develop existing applications and then operate them within a defined scope.
Technical guidance
Compare European Kubernetes providers using concrete criteria
The comparison assesses Hetzner, OVHcloud, IONOS, STACKIT, Open Telekom Cloud and Scaleway by operating model, infrastructure path and responsibility boundaries.
Technical guidance
One platform. Six entry points.
Select infrastructure and operating model deliberately
Reviews & projects
Operations that visibly relieve customers
Customer feedback on monitoring, updates, maintenance, support and stable production systems.
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT
Read client reviews
- Secure your Proxmox & backup setup
- Virtualize with Managed Proxmox
- Build a high-availability Proxmox cluster
- Modernize your infrastructure - sovereign
- Plan a sovereign open-source stack
- Integrate a local AI solution
- Modernize your legacy software
- Cut cloud cost - up to −81%
- Design an open-source AI architecture
- Get collaboration fully managed
- Ship your prototype to production
- Connect sites and clusters securely
Enquiry
Which European Kubernetes platform fits your project?
Tell us about applications, location requirements and desired ownership. We will assess provider and operating model.
- Straight with Timo and Robin - no sales team, no pitch
- A professional assessment of your situation
- Concrete next steps for infrastructure, software or AI
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.