Why I Run a Homelab

As a sysadmin, I spend most of my working hours operating systems I didn’t design, under change windows I don’t control. The homelab is the opposite of that: a place where breaking something is a Tuesday, not an incident.

A few reasons it’s stuck around longer than most hobbies do:

It’s the only place I can break things on purpose. Production doesn’t forgive experiments. A home lab is built for exactly that — try the upgrade, misconfigure the thing, watch it fail, actually understand why.

Self-hosting forces you to understand the whole stack. Running my own Nextcloud instance, for example, means owning backups, updates, and security instead of trusting someone else’s dashboard. That’s a different kind of learning than reading docs.

It’s a low-stakes way to stay current. New tools and patterns show up in the homelab world well before they’re safe to bring into a day job. Testing them at home is how I get an opinion before I need one professionally.

Future posts here will be build logs and specific changes — what I added, what broke, what I’d do differently — rather than a single “here’s my rack” post that goes stale the next time something changes.