DevOps and Kubernetes platforms
We build and run Kubernetes clusters on our own hardware, CI/CD pipelines and environments from test to canary. From compiling on the server to deployments in minutes.
- 01Kubernetes (k3s) on bare metal and Proxmox
- 02GitLab CI, container registry, canary releases
- 03Ansible, Helm, cert-manager, MetalLB, Longhorn
- 04Monitoring and logs (Prometheus, Loki, Grafana, Zabbix)
For us DevOps is not a set of tools but the answer to one question: what does it cost to ship a change safely? If the answer is "a day of work and a lot of stress", there will be few changes, and each one will be risky.
What we do
- Bare-metal Kubernetes clusters — designed and built from scratch: virtualisation on Proxmox, a highly available control plane, load balancers, distributed storage, overlay networking. We run clusters with hundreds of pods across several environments.
- CI/CD — from commit to production: build, tests, image, registry, deployment. Test, beta, canary and production environments with rolling updates and health checks.
- Legacy modernisation — moving applications from decade-old application servers into containers, step by step and backed by comparison tests.
- Infrastructure automation — Ansible for nodes, Helm for applications, certificates and DNS managed automatically.
- Observability — metrics, logs and alerts that tell you what happened before the customer calls.
Why our own clusters
The public cloud is not always the best choice — under steady load, your own hardware can be several times cheaper, and your data stays where you want it. It does require skills we have: we know how such a cluster breaks and how to fix it. We describe the details in our article on migrating to k3s.
Related reading
2026-09-25
Moving a dozen-plus applications to our own k3s cluster — problems and payoffs
Our third bare-metal Kubernetes cluster — the first in production for a client. Running since November 2023, it serves about 20 applications across four environments. The architecture, seven problems that surprised us, and what we actually gained.
2026-10-18
Kubernetes is not just a new way to deploy. It changes your operational habits
Moving applications from servers into containers is the smaller part of the job. The bigger part is dropping old habits — host monitoring, logs in /var/log, the assumption that the application runs as a single instance, and knowing which machine it runs on.
Does shipping a change still need a maintenance window?
We will help you move from manual deployments to a CI/CD pipeline and a Kubernetes cluster — on your hardware or in the cloud. We start by reviewing your current release process.