Why Every Architect Should Run a Homelab
How building a self-hosted Kubernetes cluster on ARM64 hardware has made me a better enterprise architect — and why I recommend it to every technology leader.
There’s a particular kind of knowledge you only get from running production systems yourself. Not designing them in Visio, not reviewing them in a Well-Architected Framework — actually operating them. Waking up to a failed pod, debugging a DNS issue at midnight, figuring out why your sealed secret isn’t decrypting.
For the past few months, I’ve been running a K3s Kubernetes cluster on ARM64 hardware in my home office. It hosts real services my family depends on — Nextcloud for file sharing, Immich for photo management, media services, monitoring. It’s managed through ArgoCD with a full GitOps workflow, sealed secrets for credential management, and automated deployments on git push.
What the homelab teaches that enterprise can’t
Enterprise architecture often happens at a remove from operations. You design the system, hand it to a platform team, and move on. The homelab collapses that distance entirely. When your Rancher local-path-provisioner keeps reverting its ConfigMap because K3s owns it, you can’t file a ticket — you debug it, understand the root cause, and design around it.
This kind of operational intimacy changes how you architect. You start designing for debuggability. You think about what happens when a node goes down at 2am and nobody’s awake to fix it. You learn, viscerally, why stateless services matter and why database backups are non-negotiable.
The stack
My current homelab runs K3s on a mix of ARM64 nodes, managed through a GitOps repository with ArgoCD. Every service is defined in YAML, version controlled, and automatically reconciled. I’m using sealed secrets for credential management, Helm charts for complex deployments, and Cloudflare tunnels for external access.
It’s the same patterns I recommend to enterprise clients — just at a smaller scale and with a much tighter feedback loop.
The recommendation
If you’re a technology leader or architect, build something real. Not a tutorial cluster that runs for a weekend — a platform that serves actual users (even if those users are your family). The lessons you learn will make every architecture decision you make at work more grounded, more practical, and more honest.
I’ll be writing more about specific technical decisions and patterns from the homelab in future posts. If you’re interested in the GitOps repository, it’s on GitHub.