People ask why I bother running my own infrastructure when there's a managed cloud service for everything. The honest answer: the homelab is where I learn. It's a place to break things on purpose and turn up to the day job already knowing how the moving parts behave.
The philosophy first
A homelab can sprawl into a museum of half-finished services. The rule I keep coming back to: every service has to earn its place. If it doesn't solve a real problem or teach me something, it gets turned off.
The foundation
- Virtualization & containers. A hypervisor for the things that want a whole machine, and Docker for everything else.
- Linux underneath. Most of the stack runs on Linux, because it gets out of the way.
- A segmented network. Lab gear, trusted devices and IoT live on separate VLANs with firewall rules between them. Blast radius by design.
What's earned its keep
- Self-hosted DNS and ad/tracker filtering — quietly improves every device on the network.
- Reverse proxy with automatic TLS — one clean entry point, real certificates.
- Backups that actually restore — automated, versioned, and tested by genuinely restoring them.
The real return
The homelab doesn't save me money and it isn't always convenient. What it does is make me dangerous in the good way — I've already met most problems at home before they show up at work.