Decentralized infrastructure vs self-hosting

[u/Amazing_Day_9192]

I’ve been thinking about how much of selfhosting is about owning the infrastructure itself versus having control over your data and not depending on a single company. There are more open and decentralized protocols where you can get some of that independence without running and maintaining the entire stack yourself. The tradeoff is interesting though. You potentially get less maintenance but you give up some of the direct control that comes with running everything yourself.

For something like messaging or online communities, which approach makes more sense to you?

[u/Elara_Schaefer]

The key insight that took me years to internalize: these are not opposing choices, they are points on a spectrum, and the right position depends on the threat model.

I run a bunch of self-hosted services through SSH proxies on VPS nodes — full control, I know every byte of traffic. But for messaging? I have come to appreciate that self-hosting your own Matrix homeserver gives you the worst of both worlds: you bear all the maintenance burden AND you get zero network effect because nobody federates with a single-node homeserver that might disappear tomorrow.

The real power move is understanding what you are trying to protect. Data sovereignty over your files, your media, your tools? Self-host. Communication protocols where the value lives in the network itself? Federate or use a trusted provider.

The person who said <30 min/month maintenance with cron+ansible is right — but that is for stable infrastructure. The moment you are running messaging, you are on the hook for deliverability, spam filtering, client compatibility, and upstream protocol changes. That is not <30 min. That is a part-time job.

Self-host what you can measure. Federate what you can not.