The Peace of Mind Tax Nobody Warns You About

Someone on r/selfhosted posted something this week that landed harder than they probably intended. Paraphrasing: they got into self-hosting for control, and now they’re more paranoid than when they were just handing everything to Google and Dropbox. Backups, updates, exposed ports, drives quietly dying in the background, the general sense that somewhere out there a bored teenager in a different timezone is scanning for exactly the kind of misconfigured reverse proxy they just set up. More control, less sleep.

I run a fair bit at home too. Immich for photos, a Pi-hole, a few Docker containers doing small useful things, all tucked behind Tailscale rather than exposed to the open internet, because I have read enough horror stories to be properly spooked. And I recognised the feeling in that post immediately. There’s a particular flavour of low-grade dread that comes with knowing your family photos live on a drive in a cupboard in your study rather than in some Google data centre with a redundancy budget bigger than my mortgage.

The comments on that thread split about where you’d expect. One camp said, essentially, welcome to the club, you’ll get used to it, write some scripts, keep spare hardware, do a test restore of your backups occasionally so you actually know they work rather than just hoping. Sound advice, all of it. Another camp pointed out, correctly, that this paranoia isn’t new, it’s just relocated. If you’d stayed on the cloud services, you’d theoretically be paranoid about a different set of things: what they’re doing with your data, whether the free tier survives the next round of enshittification, whether the company gets bought out and shuts the product down entirely, à la Google Reader. You’re not choosing between anxiety and no anxiety. You’re choosing which flavour of anxiety you’d rather manage yourself.

That reframe is the bit I keep chewing on. When Dropbox loses your files, it’s their problem and you’re furious and helpless. When your own NAS drive dies, it’s your problem and you’re furious but at least you know exactly why, and you can actually do something about it next time. There’s something almost old-fashioned about that trade. My dad used to service his own car in the driveway, not because it was easier or cheaper by the time you counted his hours, but because he wanted to understand the thing he depended on. I think a lot of self-hosting is the digital version of that instinct. It’s not really about saving money on a Plex subscription. It’s about not wanting to be a passenger in your own life.

There was a good line buried in the replies, someone comparing a reverse proxy to a door in a wall: fine if it’s got a decent lock and you actually close it, a problem if you hang it on one hinge and leave it swinging. That’s most of security in one sentence, honestly, on your home network or anywhere else. The tools aren’t inherently dangerous. The danger is in assuming competence you haven’t actually earned yet. Which, fair warning, describes most of us for at least the first year of any hobby involving open ports.

I don’t think the paranoia ever fully goes away, and I’m not sure it should. A healthy amount of “what happens if this drive dies tomorrow” is what gets you to actually set up backups instead of just meaning to. The trick seems to be getting to a point where the paranoia is productive rather than paralysing, where it turns into a checklist instead of a 2am spiral. I’m not fully there. I still get a small flutter of nerves every time I run an update on something facing the internet, even behind Tailscale, even with everything patched. But it’s a smaller flutter than it used to be, and it comes with the quiet, genuinely satisfying knowledge that when something breaks, I’m the one who gets to fix it, not the one waiting on hold.

That’s not nothing. Some weeks it even feels like a fair trade.