Invidious vs Seerr
| Tagline | Privacy-respecting alternative front-end for YouTube | Media request manager for Plex, Jellyfin, and Emby — fork of Overseerr |
| Category | Media Servers & Streaming | Media Servers & Streaming |
| Replaces | Netflix | Plex |
| GitHub stars | 24k | 13k |
| Language | Docker | Docker |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 3/5 Moderate | 3/5 Moderate |
| Deploy options | Docker Docker Compose Manual | Docker Docker Compose |
| Managed hosting | ||
| Last updated | 4 days ago | yesterday |
| 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.
Seerr
- No built-in media discovery beyond request management; requires a separate Radarr/Sonarr/media-server stack.
- Mobile apps are unofficial third-party clients only.
- Less battle-tested than the upstream Overseerr project given its fork status.
- No native transcoding or playback — purely a request layer.
Bottom line
Both are a similar lift to self-host; choose Invidious for the larger community and ecosystem. Seerr has seen more recent development. Open each guide below for deploy steps and the full feature gap.