WZ-IT designs, builds and operates Kubernetes platforms for production business software. From Proxmox or European cloud through GitOps and secure access to monitoring, backup and ongoing responsibility.
Kubernetes services
From target architecture through infrastructure and delivery to ongoing operations. Each page explores one part of the same accountable platform.
Kubernetes in Germany & Europe
Self-managed on cloud or bare metal, managed Kubernetes or a private platform on Proxmox: responsibilities, data location and application requirements determine the appropriate model.
Kubernetes can provide the target system for modernized or restructured applications. The architecture covers not only the cluster but also infrastructure, delivery, data, access and ongoing operations.
Assess workloads, dependencies, team, availability and cost and derive the appropriate platform from them.
Design distribution, nodes, networking, storage, load balancing and backup for bare metal, Proxmox, European providers or managed Kubernetes.
Plan containerization, configuration, secrets, data migration, deployments and rollback as one migration path.
Build observability, security, updates, restore and incident processes into the platform from the beginning.
Our primary focus is on controllable platforms on owned or European infrastructure. We integrate existing hyperscaler environments and continue operating them where that is the right technical and commercial choice.
Kubernetes on owned hardware or a virtualized private cloud, with control over compute, storage, networking and data residency.
Bare metal · Proxmox · k3s · RKE2 · Talos
Provider and architecture selection based on location, networking, hardware, compliance and operating model, without tying the platform to a proprietary service.
Hetzner · OVHcloud · STACKIT · IONOS · Scaleway
Takeover, modernization and operations for existing hyperscaler clusters as well as hybrid target architectures with explicit shared responsibility.
Amazon EKS · Azure AKS · Google GKE
The platform follows from the needs of the applications, the organization and the desired operating model.
Capture current systems, workloads, data, risks and Kubernetes suitability.
Define distribution, infrastructure, networking, storage and responsibility boundaries.
Build the platform through automation and move applications in a controlled way.
Protect testing, data migration, approval, switchover and fallback.
Organize monitoring, updates, backup, capacity and continuous evolution.
WZ-IT works with new platforms as well as existing infrastructure, applications, deployment processes, access paths or running clusters.
The decision depends on applications, scaling, availability objectives, delivery processes and the operational expertise available.
In addition to the cluster, applications need defined processes for delivery, access, observability, recovery and technical ownership.
GitOps, CI/CD, separate environments, approvals and reproducible rollbacks.
CNI, network policies, ingress or gateway, DNS, TLS and private access.
OIDC, RBAC, secrets, image validation, policies and traceable changes.
Metrics, logs, traces, alerting and SLOs for platform and applications.
Cluster state, persistent data, restore tests and a documented recovery path.
Updates, CVE assessment, capacity, costs and an agreed operating model.
Knowledge base
One accountable system
The scope can include infrastructure, application modernization, delivery, networking and ongoing operations. Responsibilities are documented for each layer and operating phase.
Move to the part of the platform that matters most for your current initiative.
Clear answers on architecture, delivery, responsibilities and ongoing operations.
Kubernetes is useful when multiple applications or teams need standardized deployments, scaling, high availability and clear platform rules. For smaller setups, Docker Compose, Coolify, LXC or VMs may meet the same requirements with less operational overhead.
No. We design self-hosted platforms on Proxmox or bare metal, Kubernetes on European cloud providers and existing managed Kubernetes environments. Infrastructure follows the requirements and responsibility boundaries.
Yes. We analyze application, data, dependencies and deployment process, containerize or replatform suitable parts and plan testing, cutover and rollback. Not every component necessarily has to run in Kubernetes.
Yes. The engagement starts with an audit and prioritized stabilization. Scope, responsibilities, monitoring, updates, backup and response model are then agreed explicitly.
No. The cluster network continues to be provided by a CNI and Kubernetes network policies. NetBird complements it with identity- and policy-based private access to the cluster API, admin tools or internal services.
Depending on the target design, we work with upstream Kubernetes and lean or hardened distributions such as k3s, RKE2 or Talos, and we also take over existing managed Kubernetes environments. The selection is made during architecture design.
Send us your starting point. We will assess which next step makes technical and commercial sense.
No risk: worst case, you leave with a clearer understanding of your project than before.


“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.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep & Robin Zins
Managing Directors of WZ-IT
