The Case for Self-Hosting Your Own Services
Cloud services are convenient until they're not. A look at why self-hosting is worth the overhead for the right workloads.
Last year Heroku killed its free tier. The year before that, a popular read-it-later service shut down with two weeks notice. Before that, Google killed Google Reader, then Inbox, then Stadia, then a dozen other things people had built workflows around.
There’s a pattern here.
I’m not writing this to be contrarian about cloud services — I use them constantly, for the right things. But I’ve also been running my own services at home for a few years now, and the case for it is stronger than most people realize.
What I actually self-host
Nothing exotic. The services I run are things I use every day:
- Nextcloud for file sync and calendar. Replaces Dropbox and Google Calendar.
- Miniflux for RSS. Replaces Feedly, which I paid for and then abandoned.
- Vaultwarden for passwords. A Bitwarden-compatible server I control entirely.
- Gitea for private Git repos. Some things don’t belong on GitHub.
- Uptime Kuma for monitoring the above.
None of these are hard to run. They’re Docker containers that start with docker compose up -d and mostly take care of themselves.
The real benefits
Control over your data. My Nextcloud files live on my hardware. My password database syncs to a server in my house. I know exactly where things are and what’s accessing them because I set it up.
No subscription creep. I was paying for Dropbox, a password manager, and a feed reader. Those subscriptions are gone. The power cost of running a small server is less than any one of them was per month.
You learn things. Running a reverse proxy, managing TLS certificates, writing backup scripts, understanding what a Docker volume actually is — none of this is academic when a service you rely on breaks at 11pm and you have to fix it. That kind of pressure teaches you faster than any tutorial.
It’s yours. The service won’t be sunset. It won’t raise prices. It won’t change the privacy policy. It won’t show you ads. The tradeoff is that you’re responsible for keeping it running, which brings me to the honest part.
The honest part
Self-hosting has real costs that people understate.
Reliability is your problem. My home internet goes down occasionally. My UPS has saved me from data corruption twice. I have automated backups that I’ve tested restoring from. None of this is hard, but you have to actually do it.
Security is your problem. Anything you expose to the internet is a target. I run everything behind a VPN (Tailscale) rather than exposing services directly. You need to keep software updated, pay attention to CVEs for things you run, and understand the attack surface you’re creating.
It’s not for everything. I still use hosted email. Running your own mail server in 2025 is a deliverability nightmare and the risk/reward doesn’t make sense for me. Some services are complex enough that the expertise required isn’t worth acquiring.
Who it’s for
Self-hosting makes the most sense if you’re already comfortable with Linux, interested in how infrastructure works, and willing to treat uptime as a hobby rather than a guarantee. If that sounds like you, the entry cost is lower than you think — a used mini PC, a few Docker containers, and an afternoon.
If you want to try it without committing to hardware, start with a $5 VPS and spin up a single service. See if you want more of that before you buy anything.
The goal isn’t to replace every cloud service. It’s to own the ones that matter to you.