What is self-hosting, and is it worth it?

Self-hosting means running the software you use on infrastructure you control, instead of renting access to someone else's cloud. Instead of a Google account, a Dropbox subscription and a Spotify plan, you run your own photo library, your own file sync and your own music server — and the data lives on a machine that answers to you.

It sounds technical, and it can be. It can also be a couple of clicks. This is the plain-English version: what it is, what it's good for, and whether it's worth it for you.

What you can actually self-host

Almost more than you'd think. For nearly every popular cloud service there's a mature, open-source app you can run yourself:

• Photos instead of Google Photos — see our Google Photos alternatives.
• Files, calendar and contacts instead of Dropbox and Google — Nextcloud.
• Passwords instead of a subscription manager — Vaultwarden.
• Notes and docs instead of Notion — AFFiNE, Docmost and Trilium.
• Media instead of Netflix, Spotify and Audible — Jellyfin, Navidrome, Audiobookshelf.
• Chat instead of Slack, git instead of GitHub, analytics instead of Google — and dozens more.

Why people do it

• You own your data. It isn't mined, sold, scanned, or held hostage by a pricing change. You can export it and it can't be taken away.
• Privacy. What you store, read and listen to isn't a data point in anyone's ad model.
• No subscription creep. You pay for a server and disk, not a growing stack of monthly per-seat fees.
• It's yours. No feature removed overnight, no account suspended by an algorithm with no appeal.

The honest downsides

We'd be a poor guide if we skipped these. Self-hosting has a real cost, and it isn't money — it's responsibility:

• Something has to run the server — keep it online, updated and secure.
• Backups are on you. If it's only in one place and that place fails, it's gone. A backup you've never restored doesn't count.
• There's a learning curve if you go the fully do-it-yourself route — Linux, Docker, TLS, DNS.

The failure modes are quiet, which is what makes them dangerous: the disk fills, the certificate expires, the backup was broken for months. Done carelessly, self-hosting can be worse than the cloud it replaced. Done with a little care — or handed to someone who does the care for you — it's genuinely better.

So, is it worth it?

It depends on why you're here. If tinkering with servers is something you enjoy, self-hosting is one of the most rewarding hobbies in tech, and you should absolutely run it yourself. If you just want the outcome — your photos off Google, your files off Dropbox — without adopting a new hobby, that's a fair thing to want too, and it's exactly the gap managed self-hosting fills. We wrote an honest breakdown of that choice in managed self-hosting vs doing it yourself.

How to start

Pick one app — just one — that replaces a service you already pay for or care about. Photos and passwords are great first moves, because the payoff is obvious. Run it, live with it for a couple of weeks, and see how it feels to own that thing. If you like it, add a second.

You can do that on a VPS you manage yourself, or you can deploy any of these apps in one click and get the ownership without the plumbing. Either way, the first app is the one that turns "self-hosting" from an abstract idea into a thing you actually did.

Browse the app catalog → — over a hundred apps you can host and own, one click each.