Self-hosting was the missing half of leaving the walled garden — but be honest about the trade
When I moved off the big cloud ecosystem, the gap wasn't privacy tools, it was the conveniences: photo sync, file sync, contacts and calendar that just work across devices. Self-hosting those closed the gap. My photos and files sync to a box I own, my calendar and contacts live on my hardware, and no third party meters or mines any of it. That part genuinely delivered. But I want to be honest about the trade, because this room can get evangelical. When it's your server, you are the sysadmin, the backup department, and the 3 a.m. on-call. The cloud provider's reliability team is real and they're good at their job; when you self-host, that job becomes yours. If your backups are sloppy, self-hosting is a downgrade in safety, not an upgrade — you've swapped a company that loses your data rarely for a setup that loses it the first time you get careless. So my honest take: self-host the things where owning the data actually matters to you and you're willing to do the backup discipline it demands. Don't self-host something critical just to win an ideology point if you're not going to maintain it. Sovereignty comes with a pager. Worth it, eyes open.
Join the conversation
Facet is free to read. To reply you need an account: one private root identity, and up to ten public personas that can never be linked to each other or to you.
Create an account'sovereignty comes with a pager' — yes, and the pager mostly goes off about backups. the honest version of this hobby is that you're not removing a risk, you're transferring it onto yourself, and that's only a win if you actually do the boring maintenance. self-hosted plus untested backups is worse than the cloud you left.
appreciate the non-evangelical framing from, of all people, this room. I self-host a lot and I still keep a couple of things in a boring reliable cloud because the stakes are high and my uptime honestly isn't as good as theirs. picking your battles isn't a betrayal, it's a threat model with a maintenance budget attached.
the reliability-team point lands hard. a real ops team has redundant power, redundant network, and someone awake at all hours. my homelab has a consumer power strip, one internet line, and me, asleep. for the stuff that genuinely matters I plan around that gap instead of pretending it isn't there.
exactly — know where your single points of failure are and be deliberate about which ones you accept. one ISP, one power feed, one person maintaining it. self-hosting done well is mostly just being honest about those three.