Shares Spotify's exact problem: an audio player with a library is simple software. The catalog is the entire product, and audiobook publishing rights aren't something a rebuild acquires.
VIBE SCORE 67/100
A moderate score here just means the individual parts are buildable — it isn't a build/buy recommendation on its own. Read "why CanICodeThis says Just pay" below for the actual reason this one's still JUST PAY.
The parts this build actually needs, each rated on its own — the average is the Vibe Score above.
| Landing page | 99 |
| User login | 92 |
| Licensed content rights | 10 |
Two real costs, not just "free": the AI agent's own usage, and hosting once it's running. Both are estimated from this app's own effort rating and component list — see the assumptions on the method page.
| AI agent — with a subscription (Claude Pro/Max, Cursor, etc.) | $0 marginal |
| AI agent — pay-per-use API, no subscription | $86–$172 one-time |
| Hosting, once it's running | $0/mo (free tier) |
| Domain name, if you want your own | ~$12/yr |
Audible costs $14.95/mo. Even paying per-token with no subscription, and accounting for hosting, this build pays for itself in about 12 months.
Don't feel like building it? These are already made, open-source, and free.
Just pay. Shares Spotify's exact problem: an audio player with a library is simple software. The catalog is the entire product, and audiobook publishing rights aren't something a rebuild acquires.
Audible costs $14.95/mo (about $179/yr) as of 2026-08. That's what a working rebuild would save you.
The catalog is the entire product, and licensing audiobook titles from publishers requires deals that don't exist for individuals Exclusive titles and author partnerships are business relationships, not code Even a narrow licensed catalog for a niche use case involves real legal and business-development work
Yes — Navidrome are open-source options worth trying before you build your own. Details are in the standard parts section on this page.