Invidious vs Readarr
| Tagline | Privacy-respecting alternative front-end for YouTube | Ebook and audiobook collection manager with automated downloading |
| Category | Media Servers & Streaming | Media Servers & Streaming |
| Replaces | Netflix | Plex |
| GitHub stars | 24k | 3.5k |
| Language | Docker | C# |
| License | AGPL-3.0 | GPL-3.0 |
| Self-host difficulty | 3/5 Moderate | 3/5 Moderate |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 4 days ago | 1 year ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Invidious
- Relies entirely on YouTube's infrastructure; Google can and does throttle or break the API at any time.
- No support for YouTube Shorts, YouTube Music, or YouTube Premium content.
- Comment loading and search quality degrade as Google tightens API restrictions.
- No upload capability; purely a viewing front-end.
Readarr
- Still considered beta; metadata matching can be unreliable for some editions
- Requires Calibre or Calibre-web for full library management features
- No built-in reader; content serving requires a separate ebook server
Bottom line
Both are a similar lift to self-host; choose Invidious for the larger community and ecosystem. Invidious has seen more recent development. Open each guide below for deploy steps and the full feature gap.