Jellyseerr
Self-HostedOpen-source media request management for Plex/Emby (Sonarr/Radarr compatible)
Overview
Jellyseerr streamlines media request management for self-hosted Plex/Emby setups. Users can request movies and TV shows, which auto-add to Sonarr/Radarr for downloading. It syncs with your libraries to avoid duplicates, offers user permission controls, custom request forms, and notifications (Discord, email). Deploy via Docker (simple compose files) or binary—lightweight, customizable UI, ideal for families/communities sharing a server, centralizing requests without manual work.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
jellyseerr:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: jellyseerr
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Auto-sync with Sonarr/Radarr for request fulfillment
- Plex/Emby library integration to avoid duplicate requests
- User permission controls & custom request workflows
- Multi-channel notifications (Discord, email)
Frequently Asked Questions
? Is Jellyseerr hard to install?
No—Jellyseerr is easiest to deploy via Docker using the official image and compose files. Minimal configuration is needed if you already have Sonarr/Radarr/Plex set up; just link services via API keys.
? Is it a good alternative to Overseerr?
Yes—Jellyseerr is a fork of Overseerr with improved UI, faster performance, and better Sonarr/Radarr integration. It’s a top choice for users seeking a polished open-source alternative.
? Is it completely free?
Absolutely—Jellyseerr is 100% open-source and free to use. No paid tiers or hidden fees; all features are available for self-hosters.
Top Alternatives
People Also Ask about Jellyseerr
Tool Info
Pros
- ⊕ Privacy-focused (self-hosted, no third-party access)
- ⊕ No subscription fees or paid tiers
- ⊕ Polished UI and faster performance than legacy alternatives
- ⊕ Seamless integration with popular self-hosted media tools
Cons
- ⊖ Requires existing Sonarr/Radarr/Plex/Emby setup to be useful
- ⊖ Initial configuration needs API key setup for linked services
- ⊖ Limited to self-hosted ecosystems (not for cloud media services)