Infrastructure & Self-HostingStatus: Ongoing

Home Lab

My home lab is where I learn how the infrastructure behind applications actually works, by running it myself. It's a long-running, always-evolving environment for virtualization, networking, and self-hosted services.

My role
Personal project: design, setup, and ongoing maintenance
Topics
Virtualization · Networking · Self-hosting · Linux

The Idea

Most of the software I work with runs on infrastructure I never see. The home lab is my way of closing that gap: building and operating the layers underneath applications so I understand the trade-offs involved, not just the abstractions.

What I Built

At a high level, the lab is a small virtualized environment where I run self-hosted services, experiment with networking, and try out new tools. It changes regularly as I take on new experiments.

Challenges & Decisions

Running your own services also means being responsible for securing them. With a cybersecurity background, I try to approach the lab deliberately: keep the footprint small, be careful about what is exposed, and treat every new service as something to maintain, not just install. For the same reason, I keep the specifics of my setup private.

What I Learned

Operating infrastructure, even at home scale, teaches things that are hard to learn otherwise: how small configuration choices compound, why good defaults and documentation matter, and how much of reliability comes down to keeping things simple.

Current State

Ongoing. The lab is never really finished; I add, rebuild, and retire pieces of it as I learn.