Updated 2026-11-13
Self-hosted music and audiobooks for a family: why two apps is the wrong answer
Short answer: the software already exists and it is good. Navidrome handles music, Audiobookshelf handles audiobooks, and both are free. What does not exist is a household product: one place where a parent's library, a teenager's playlists and a child's bedtime book all live with separate progress and separate permissions. The two-app answer is technically correct and fails the actual request. The business is not another server. It is hosting the two servers for people who will not run Docker.
🔥 Heat 171.94
1 evidence post
3 pain points
2026-11-13
Mention 1 · 1 source🔥 Surging
At a glance
Who buys
Households of 2 to 6
Own a NAS or an old desktop. Paying for Spotify Family and a Plex pass today.
What they pay today
$21.99 a month for Spotify Family
US price after the January 2026 increase. Plex Lifetime went to $749.99 in July.
First revenue
60 to 90 days, hosting only
The software is free and stays free. The service is what sells.
Cost to build v1
1 week for a bundle, 3 months for hosting
Two containers, one reverse proxy, one backup job.
Up against
6 servers, 0 household products
Navidrome, Audiobookshelf, Jellyfin, Plex, Emby, Airsonic.
Ceiling
Medium, with high retention
Families churn slowly. That is worth more than the market size suggests.
Sources: Billboard, 2026-01-15, on the US Spotify increase; Pinggy, 2026-06-06, and Hosting Infos, 2026-09-05, on the Plex Lifetime change announced in May 2026 and effective 2026-07-01.
What one household actually asked
“looking for a way to keep a family music library and some audiobooks on a home server, so playback does not depend on a streaming subscription.”
The goal is not self-hosting. The goal is independence from a subscription that keeps raising its price. Self-hosting is the means.
“not trying to build a huge media stack, just these two jobs.”
This is the constraint every self-hosting guide ignores. The recommendations are built for people who enjoy building the stack. This person wants two jobs done and nothing else.
“has anyone here run one of these for a household, or is there a reason to pick a different tool for music vs audiobooks?”
The question is the product. Nobody has answered it with a household-first setup, so the answer arrives as two apps, two accounts, two libraries and a shared folder.
Why now
1. Three subscription prices moved within seven months
In January 2026 Spotify raised US prices: individual from $11.99 to $12.99, Family from $19.99 to $21.99, Duo from $16.99 to $18.99. In May 2026 Plex announced that its Lifetime Pass would go from $249.99 to $749.99 as of 1 July, a threefold increase, and that remote streaming of your own library would require a subscription rather than being free. In July 2026 Apple Music raised prices for the first time in nearly four years.
Three increases in one year, from three different companies, all aimed at the same household budget. The person who tolerated $19.99 for a family plan now sees $21.99 plus a Plex subscription for the privilege of streaming files they already own.
Billboard, 2026-01-15, and 2026-07-17; Pinggy, 2026-06-06; OpenSourceProjects.cc, 2026-11-10, on remote streaming moving behind a subscription.
2. The open-source side finally has both halves
Navidrome covers music with a Subsonic-compatible API and clients on every platform. Audiobookshelf covers audiobooks and podcasts with per-user progress, multi-user permissions, chapter editing and offline listening in its mobile apps. Jellyfin does both, less elegantly, under a GPL license. Five years ago this request had no clean answer. Today it has two, and that is the problem.
Audiobookshelf documentation; Serverside, 2026-08-31, comparing Jellyfin, Plex and Emby.
3. Plex's 2024 privacy episode created a pool of people already looking
When Plex changed its privacy terms in 2024, a visible share of heavy users moved to Jellyfin. That migration did not finish. Those users kept the hardware, kept the library, and kept the habit of checking what the commercial option does next. They are the warmest audience a self-hosted household product will ever get.
The gap: nobody ships a household
The software map is full. The product map is empty.
- Navidrome: excellent music server, one library, one admin. Household member management is basic and there is no audiobook concept at all.
- Audiobookshelf: the best audiobook experience in open source, with per-user progress that syncs across devices. It does not play music.
- Jellyfin: does both under one roof and one login, which is closer to the request. Music handling is serviceable rather than good, and audiobook progress tracking is the weak half.
- Plex and Emby: do both well and charge for it, which is the thing this household is trying to escape.
- Airsonic and forks: music only, older interface, effectively a legacy option.
What "household" would actually require
One login per family member, with a parent account that can see what the kids can see. Separate listening progress for the same audiobook, because a parent and a child read at different speeds. One library where a bedtime story and a road-trip playlist are both reachable from the same app. A backup that restores metadata, not just audio files.
None of that is a feature gap in one server. It is a missing product that sits above two servers, and it is exactly why the thread's question has no satisfactory answer.
Reasons to build
- The price increases are recent and repeated. January, May and July 2026 each moved a subscription this household pays for. Demand is being refreshed by the vendors themselves, which is the cheapest acquisition channel available.
- The software is free, so your cost of goods is your own time. You are not building a media server. You are configuring two that already work, and the marginal cost of one more household is a container and a backup job.
- Retention is the product. A household that moves its library off Spotify does not move it back the next quarter. The switching cost is re-importing a library and re-training a family, which is exactly the kind of friction that makes a small subscription durable.
- The honest answer is already written in the thread. "Two apps" is the technically correct reply and the person asked whether there is a reason to split them. A product that says "no, here is one" answers a question people are actively asking.
Reasons not to build
- The software is free and the audience knows it. Every component you would bundle is open source and one search away. Charging for a Compose file in a community that trades configs for free is a hard sell, and the "just use Navidrome" comment will appear under every post you make.
- Support load is permanent and personal. A family media server breaks when a drive fills, a certificate expires, a mobile app updates or a router changes. Your customers are not sysadmins, so every one of those becomes a message to you at 9pm. This is the real cost, and it does not decrease with scale until it becomes a full time job.
- Legal exposure on the content side. Music licensing is not a gray area you can ignore forever. A product that helps households build libraries has to be explicit about what it does and does not do, and the careful wording costs conversions.
- Plex can reverse the price increase. A single announcement undoes a large part of the urgency, and the 2026 increases are recent enough that a correction is plausible. Your demand curve is partly rented from a competitor's pricing decision.
If you build it anyway
Do not build a media server. Build the household layer and the hosting. The first version is a managed instance per household: Navidrome and Audiobookshelf behind one login, one reverse proxy with automatic certificates, daily metadata backup, and a mobile-first setup flow where a parent creates accounts for the family in five minutes.
The one feature that decides whether this works is audiobook progress that survives a device change, because that is what makes a household trust you with the library. Get that right before adding anything else.
What you would charge
- $8 a month per household, priced clearly under Spotify Family at $21.99 so the comparison is obvious without a calculator.
- A $79 one-time option for people who already have hardware and want the setup done, with no ongoing support. This converts the self-hosters who will never pay monthly into revenue at the moment they are most willing.
- No per-user pricing. A household plan that charges per child is the same trap Spotify is in, and the whole point is leaving it.
Napkin math
Assumptions, and the support line is the one that decides this.
- Year one: 200 households at $8 a month, averaging 9 months of tenure, equals about $14,400 gross.
- Server cost per household at small scale: roughly $5 a month for storage and compute, so $9,000 across the same period.
- Support: 200 households generating one ticket per quarter at 20 minutes each is about 67 hours a year, unpaid and unbudgeted.
Gross margin lands around 38 percent before your own time, which is thin for a subscription. The path to a real business is not more households at $8. It is the $79 setup fee and a higher tier for families that want photo backup in the same box. That is a different product than the one in the thread, and it is the one that pays.
Evidence (1 post)
r/selfhosted, 2026-11-13. Price figures come from Billboard, Pinggy and OpenSourceProjects.cc, each dated inline.
FAQ
Can one app serve both music and audiobooks?
Jellyfin can, under one login, and it is the closest existing answer. Its music handling is serviceable and its audiobook progress tracking is weaker than Audiobookshelf's. That gap is the reason the standard advice is still two apps.
What does the household save?
Spotify Family is $21.99 a month in the US after the January 2026 increase, or about $264 a year. A self-hosted setup replaces that with electricity and storage you already own, plus your time on maintenance.
Why did Plex users leave in 2024?
A privacy terms change pushed a visible share of heavy users to Jellyfin. Most kept the hardware and the library, which makes them the most likely first customers for a household-focused self-hosted product.
What is the hardest part of building this?
Not the server. The support. A media server breaks when a disk fills, a certificate expires or a mobile client updates, and your customers are families rather than sysadmins. That load is permanent and personal.
Is charging for this realistic?
For the software, no, because every component is free and one search away. For hosting and setup, yes, because the people who ask this question are precisely the ones who do not want to run Docker themselves.
How is this data collected and verified?
Price changes are cited from Billboard, Pinggy and Hosting Infos with publication dates. Software capabilities come from project documentation. Quotes link to the original thread. See how data is collected.
One new evidence-backed need every day. Every trend traced to the original post and the exact quote.
Subscribe $19.99/mo →