The Lab

There was a time when running your own email server, web host, and file storage was normal. Then the cloud happened, and most of us traded control for convenience. That trade made sense — cloud services are easier, more reliable, and often cheaper than maintaining your own infrastructure. But something was lost in the process: the understanding of how things actually work.

Self-hosting is my way of keeping that understanding alive. When a container crashes, I am the one who reads the logs and fixes it. When a certificate expires, I am the one who renews it. When a new tool looks interesting, I am the one who deploys it, configures it, and decides whether it is worth keeping. This hands-on engagement with infrastructure makes me a better technologist at work, not just at home.

There is also a privacy dimension. Every service I self-host is one less service sending my data to a third party. My AI chats stay on my server. My media library stays on my drives. My remote desktop sessions stay within my network. That does not mean I self-host everything — some services are better left to companies with dedicated teams and SLAs. But where it makes sense, I prefer to own the stack.