Why This Blog Exists
I didn't set out to write a blog about self-hosting. I set out to solve a series of small, practical problems — where do my files live, who can read my notes, what happens to my photos if a company changes its terms of service. Somewhere along the way, I noticed the same answer kept showing up: build it myself, and understand it well enough to trust it.
That pattern is what this blog is actually about.
It Started with Small Decisions
A few years ago, I started moving pieces of my digital life out of the big platforms, one at a time. My files went from OneDrive to a NextCloud instance running on a small server in my home. My notes went from OneNote to Obsidian, with the underlying files versioned in a private GitHub repository instead of sitting on Microsoft's servers. None of these felt like a grand statement at the time — they were just projects. Interesting technical problems to solve on a weekend.
It was only in hindsight that I noticed the thread running through all of them: control. Not paranoia, not a desire to disappear off the grid — just a plain wish to know where my data actually lives, who can access it, and what happens to it if the company behind it makes a decision I disagree with.
Why It Matters More Now
That instinct has felt more relevant lately, and I don't think that's a coincidence. The last year has made a lot of people — especially in Europe — think harder about how much of their digital life sits on infrastructure controlled by a single country, subject to that country's laws and that country's politics. Watching the current political climate in the United States has pushed many individuals and organizations to actively move their data out of American cloud services, wherever that's practically possible.
For people who aren't technical, that's a genuinely hard problem. You can't easily "just move" your photos, your documents, and your communication history without real friction, real risk of data loss, and real time investment. I'm fortunate enough to have the technical background to do it myself — a background rooted, in part, in my years with the Danish Home Guard and a signals background that trained me to think carefully about communication, resilience, and what happens when the infrastructure you normally rely on isn't there.
That last part matters more than it might seem. My interest in self-hosting isn't purely about corporate data policies — it connects to a broader instinct toward self-sufficiency. The same thinking that makes me want to control where my files live is the thinking that makes me interested in mesh networking that doesn't depend on centralized infrastructure, or in being prepared to look after my family if the systems we normally take for granted stop working, even temporarily. Digital independence and practical resilience turn out to be the same muscle, just exercised in different contexts.
What This Blog Actually Is
This isn't a blog with a single, narrow focus. It moves between homelab infrastructure, radio and signals, AI agents and automation, and occasionally something more reflective. That might look scattered at first glance. It isn't, really — every post here comes back to the same underlying question: what do I actually control, and what am I quietly outsourcing to someone else?
Sometimes the answer is technical: a Proxmox configuration, a Docker stack, a stubborn Cloudflare Tunnel timeout. Sometimes it's more conceptual: what does resilience actually mean, and where's the line between healthy self-sufficiency and unnecessary paranoia.
I don't think everyone needs to run their own cloud, encrypt their own notes, or study mesh networking protocols. But I do think it's worth understanding what you're trading away every time you choose convenience over control — even if, after thinking it through, you decide convenience is the right trade for you. That understanding is the actual point of this blog. The homelab is just where I happen to work it out.