Quanby Lab
Our reference Kubernetes platform
This is how we build a Kubernetes platform when we start from scratch: proven open source, everything in Git, nothing configured by hand. Explore the layers and click any component to see what it does and why it’s there.
Where it runs
Cluster foundation
Provisioned with
Network & access
Data
Security
Source of truth
Automation
Environments
Collect
Understand
Act
Principles
What every platform we build has in common
Everything in Git
Infrastructure, platform and applications are code. Every change is reviewed, traceable and reversible.
Immutable by default
No hand-tuned servers. Nodes are replaced, not repaired, so every environment stays identical.
Secure from the start
Network policies, admission policies and external secrets are part of the base, not an afterthought.
Restores that are tested
Backups are only useful if they come back. We test restores on a schedule and document the result.
Observable end to end
Metrics, logs and alerts from day one, so problems are visible before your customers notice them.
Portable, no lock-in
Open-source components that run the same on bare metal, Proxmox or any cloud provider.
Your stack, not ours
Already running Kubernetes? We start from what you have.
This reference architecture is our starting point for new platforms, not a requirement. A stable cluster on a managed service stays where it is. We improve its upgrades, security, backups and monitoring, and only suggest a migration when it clearly pays off.
- Azure AKS
- Amazon EKS
- Google GKE
- Red Hat OpenShift
- Hetzner & OVHcloud
- Self-managed & on-premises
Let’s talk
Need Kubernetes expertise?
Whether you’re dealing with a production issue, planning an upgrade or looking for a long-term engineering partner, we’d like to hear about it.