Self-Hosting Isn't Free: The Hidden Cost of "Freedom" and Why Families Deserve Better

Self-hosting your audio library is powerful, and it’s not free — not in the way “free and open source” usually implies. The software genuinely costs nothing. Running it costs real time, indefinitely, and that’s worth saying plainly instead of glossing over.

The stack underneath “just self-host it”

A typical self-hosted audio setup — Audiobookshelf for audiobooks and podcasts, Navidrome or Jellyfin for music — is genuinely free software. Getting it running reliably, and reachable from outside your house, usually also means setting up:

• Docker and Docker Compose, on most NAS models and any spare PC
• A reverse proxy, if you want one clean address instead of a list of ports
• TLS certificates, if that proxy is doing HTTPS
• Either port forwarding and dynamic DNS, or a tool like Tailscale or Cloudflare Tunnel — the two we’d actually recommend, and the ones covered in our full setup guide
• Whatever backup routine actually gets a copy of the library off that one box

None of these are exotic on their own. Together, for a first-timer, they’re a genuine weekend — and they don’t stay done. Updates land, something occasionally breaks after one of them, and someone has to notice.

The updates don’t stop after setup

The weekend you spend getting Audiobookshelf, Navidrome, and a reverse proxy running is the visible cost. The one that keeps showing up afterward is smaller but never actually ends: the NAS’s operating system wants updates, Audiobookshelf and Navidrome each ship their own, and a TLS certificate from Let’s Encrypt expires every ninety days unless something is renewing it automatically. None of these are individually hard. But each one is a small task with no fixed end date, arriving on its own schedule for as long as the setup exists — which is exactly the kind of cost that’s easy to underestimate from a Saturday when everything just worked.

The backup is a second system, not a checkbox

Everything above is what it takes to get a library running and reachable. It says nothing about protecting it, which is a separate piece of work with its own ongoing cost. The standard advice in self-hosting circles is the 3-2-1 rule: three copies of the data, on two different kinds of storage, with one of them somewhere else entirely — a different building, ideally. In practice that means a second local copy (an external drive, or a second bay in the NAS) plus an automated sync to somewhere offsite, since a fire, flood, or theft can take out every copy that’s still in the house.

Most self-hosted setups get the working copy right and stop there. RAID, if it’s configured, protects against one drive failing — it does nothing against a deleted file, a corrupted database, or the box itself being destroyed, because every drive is still in the same room. Setting up the offsite piece properly is maybe an hour of work the first time. It’s also the piece that’s easiest to skip, because skipping it doesn’t cost anything until the one day it would have mattered.

Someone becomes the sysadmin

This is the part that doesn’t show up in most “how to self-host” guides: once it’s running, one person in the household owns it. Usually whoever set it up. They’re the one who updates the apps, replaces a failed drive, fixes the reverse proxy when a certificate expires, and walks a parent or a kid through logging in on a new phone.

That’s not a criticism — plenty of people on r/selfhosted and r/DataHoarder genuinely enjoy exactly this, and are glad to be the one their family calls. But it means the household isn’t really paying for “free” software with money; it’s paying with one person’s ongoing attention, for as long as the setup exists. That’s a real cost, even though no invoice ever states it.

When self-hosting is genuinely the right call

If maintaining a small server is something you’d do anyway — for the learning, for the control, for the satisfaction of it — self-hosting an audio library is a great decision, and Audiobookshelf specifically is excellent software, built by people who clearly listen to audiobooks themselves. This isn’t an argument against that. It’s aimed at the households where nobody actually wants that role, and “just self-host it” quietly assumes someone will take it anyway.

What we’re building instead

own.audio exists for that second group: one place for the family’s audiobooks, music, and stories, without anyone in the house needing to become its administrator. No Docker, no certificates, no one person the rest of the family depends on to keep it working.

It’s still in development. Register on the front page if you want to know when it’s ready.