Why Self-Hosting Is Having a Moment
Docker made it easier. But the real driver isn't technical enthusiasm — it's something that happened to trust.
In 2023, Evernote cut its free tier to a single notebook and 50 notes. Millions of people had spent years building their knowledge system inside it — clipped articles, project notes, meeting summaries — and one pricing change made all of that feel precarious. Some moved to Notion. A smaller group did something different: they installed Docker, stood up a local instance of Joplin or Silverbullet on a machine at home, and moved everything there.
That's self-hosting. And the reason it's spreading isn't what most people assume.
The wrong explanation
The usual story is that self-hosting is a privacy play. You don't want Google reading your photos. You don't trust Dropbox. You're technical and mildly paranoid. There's some truth to this, but it misses what's actually driving the movement.
CISPA researchers found that roughly 8.4% of the US population has tried self-hosting — around 28 million people. That's not a fringe hobby. And when you look at why, the dominant theme isn't surveillance fear. It's the accumulation of smaller disappointments: a price increase, a feature removed, an acquisition that went sideways, a free tier quietly made unusable. Trust failures, not paranoia.
Evernote is the canonical example, but it's not alone. Fitbit was acquired by Google. LastPass had a security incident that shook confidence. Heroku killed its free tier in November 2022. The message these events sent, individually and together, was: you've built something important on ground that someone else owns, and they may move it.
Self-hosting is the counter-move. Not to every service — that would be unlivable — but to the ones where the data matters enough to be worth protecting.
What Docker actually changed
Five years ago, self-hosting meant wrestling with servers, managing dependencies by hand, fighting configuration files in obscure formats. It was genuinely hard. The kind of thing you'd spend a weekend on and still not be sure it worked.
Docker changed that equation more than any other single technology. A docker compose up command can now spin up Immich (a Google Photos alternative), Paperless-ngx (document management), or Jellyfin (media streaming) in minutes, on a $300 mini PC or a cheap VPS. The dependency hell that made self-hosting feel like a full-time job mostly disappeared.
The r/selfhosted community now has over a million members. Their 2024 survey found that 97% of respondents use containers. Docker became the distribution format that made the ecosystem viable — and, not coincidentally, made it something you could recommend to a technically curious friend without immediately triggering regret.
The honest cost calculation
Self-hosting is not free.
The server costs something. Even if it's a Raspberry Pi, that's hardware, electricity, your home network. But the bigger cost is time: security patches, updates, occasional broken containers, backups you have to remember to set up yourself. A small home server running eight services will need a few hours of attention a month if you're doing it properly.
The math only works in your favor if you're replacing services you'd actually pay for. One developer calculated they save about $100 a year in subscription fees by self-hosting six apps. That's real, but it's not a windfall. The calculation shifts once you account for the value of the control itself: knowing your photos won't disappear if a company shuts down a product, that your document archive doesn't depend on someone's funding round.
Self-hosting is often a premium paid for certainty, not a savings strategy. That's worth naming clearly, because the enthusiast framing tends to obscure it.
When it actually makes sense
Not everything should be self-hosted. Email is a famous trap — the infrastructure required to run a reliable mail server that doesn't end up in spam filters is substantial, and most people who try eventually give up. Real-time collaboration, calendar sync, anything that needs to be available instantly across devices: the convenience of hosted services is usually worth the tradeoff.
Where self-hosting makes sense is a narrower category. It tends to be: durable personal data (photos, documents, notes) you'd want to keep for decades and can't afford to lose to a company pivot. Services where the data is sensitive enough that cloud storage feels uncomfortable. And tools where you care about customization enough to run your own instance.
The pattern that emerges is less "opt out of the cloud entirely" and more "be selective about which relationships require that you own the asset."
The thing underneath
Harbor is self-hostable because I think the choice should exist. A personal knowledge base isn't the same as a streaming service. The decisions you write down, the people you track, the context you build over years — that's the kind of data where the relationship with the service matters. Whether someone uses the managed version or hosts it themselves, it should at minimum be something they could leave.
The self-hosting movement, underneath the container configs and subreddit recommendations, is about a recalibration that happened quietly over several years. Not a blanket rejection of cloud services. Something more specific: the recognition that convenience and control sit on a spectrum, and the right position on that spectrum depends on what's actually at stake.
It's not really a trend. It's what happens when enough promises get broken.
Asgeir Albretsen is the founder of Harbor.