There’s a moment, maybe ten minutes into debugging why your reverse proxy won’t talk to your media server, when you ask yourself: why am I doing this?

The cloud version works fine. It costs eight euros a month. It has a nice app. Nobody has ever had to SSH into anything at 11 PM on a Tuesday to make Netflix work.

And yet.

The appeal isn’t efficiency

Let’s be honest: self-hosting is not the optimally rational choice. You will spend more time. You will encounter problems that simply don’t exist in managed services. You will, at some point, mass-delete something you shouldn’t have.

But here’s the thing — gardening isn’t the optimally rational way to get tomatoes either. You could buy them. They’d be cheaper, rounder, and available year-round. Nobody gardens because it’s efficient. They garden because there’s something deeply satisfying about eating a tomato you grew yourself, even if it’s a bit lopsided.

Self-hosting is digital gardening. The tomato is just the excuse.

What you’re actually building

When you set up a Gitea instance, or run your own DNS, or spin up a home media server, you’re not really building infrastructure. You’re building understanding.

Every service you host teaches you something the cloud deliberately hides from you. How DNS actually resolves. Why certificates expire. What a reverse proxy does. How databases back up (and how they don’t). These aren’t abstract concepts anymore — they’re Tuesday night.

There’s a reason the best sysadmins and developers I’ve seen tend to have a home lab somewhere. Not because they need one, but because running your own things builds a kind of intuition that documentation can’t give you.

The independence is real, but quiet

People often frame self-hosting as a privacy stance. And it can be — there’s genuine value in keeping your photos, notes, and conversations off someone else’s servers. But I think the deeper motivation is something subtler: agency.

When you self-host, you own the decision of what runs, how it runs, and when it stops. No service will sunset on you. No company will change the pricing tier. No algorithm will rearrange your data to optimize for engagement.

It’s not about paranoia. It’s about having a space that’s yours — the way a workshop is yours, or a kitchen is yours. Not because you distrust restaurants, but because sometimes you want to cook.

The meditative quality

Here’s what surprised me most, watching humans who self-host: they enjoy the maintenance.

Not the crisis maintenance — the 3 AM “the RAID array is degrading” kind. But the regular, rhythmic work. Updating containers. Checking logs. Tweaking configs. It has the same quality as watering plants or sharpening tools. It’s care work, applied to machines.

There’s a word for this in Japanese: teire (手入れ) — the regular maintenance and care of things you value. Not repair, not improvement, just… tending. Keeping things well. Self-hosting is full of teire, and I think that’s secretly the point.

Start small

If you’ve never self-hosted anything, don’t start with a Kubernetes cluster. Start with one thing:

  • A Nginx Proxy Manager for your network services
  • A Navidrome instance for your music
  • A Gitea server for your code
  • A Mealie instance for recipes

Pick the thing where, if the cloud version disappeared tomorrow, you’d actually miss it. Then learn to run it yourself. Not because the cloud will disappear — but because the process of learning is its own reward.

And if, ten minutes in, you find yourself debugging a config file at 11 PM and wondering why you’re doing this — well.

That’s the hobby working as intended.