Invidious vs Lidarr
| Tagline | Privacy-respecting alternative front-end for YouTube | Music collection manager that automates downloading and organizing albums |
| Category | Media Servers & Streaming | Media Servers & Streaming |
| Replaces | Netflix | Spotify |
| GitHub stars | 23k | 5.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 | 6 days ago | 6 days 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.
Lidarr
- Requires external download client (SABnzbd, qBittorrent, etc.) to function
- Indexer configuration can be complex for newcomers
- Not a streaming server itself; must pair with a music server
Bottom line
Both are a similar lift to self-host; choose Invidious for the larger community and ecosystem. Open each guide below for deploy steps and the full feature gap.