Jellyfin household request portal
friends/family request content
// official site: docs.jellyseerr.dev ↗
MEDIA STACK · PRO TIER
Jellyseerrpro
Jellyseerr is a fork of Overseerr with Jellyfin authentication support — same request management + discovery UX, but works with Jellyfin (and Emby, and Plex). For households on Jellyfin specifically, Jellyseerr is the right choice.
// What it is
A closer look.
Jellyseerr is a fork of Overseerr with Jellyfin authentication support — same request management + discovery UX, but works with Jellyfin (and Emby, and Plex). For households on Jellyfin specifically, Jellyseerr is the right choice.
Functionally identical to Overseerr for the core flow; the difference is auth: Overseerr is Plex-first, Jellyseerr supports all three media servers.
// Use cases
What it's for.
Concrete scenarios where teams pick Jellyseerr over the SaaS alternative.
Multi-server support
Jellyfin + Emby + Plex auth in one tool
Media discovery
TMDB browsing
Request approval workflow
admin oversight
Per-user permissions
granular control
// Who it's for
Built for these teams.
If your team profile matches one of these, Jellyseerr is a strong fit out of the box.
Jellyfin-primary households
(the typical use case)
Multi-media-server operators
running Jellyfin + Plex side-by-side
Privacy-conscious cord-cutters
preferring Jellyfin to Plex
Family sharing setups
on Jellyfin
Open-source-only operators
rejecting commercial Plex
// Differentiators
Why teams pick Jellyseerr.
When evaluating self-hosted options for this category, here are the dimensions on which Jellyseerr consistently lands above the alternatives.
- ✓MIT license — (fork of Overseerr) — fully open
- ✓Jellyfin native — Plex-only Overseerr can't auth Jellyfin users
- ✓Tri-server support — Jellyfin + Emby + Plex
- ✓Sonarr / Radarr integration — same as Overseerr
- ✓Active development — strong fork maintenance
- ✓UI / UX matches Overseerr — easy onboarding for Overseerr users
// Integrations
Connects to.
The stack you'll plug Jellyseerr into — services, protocols, and adjacent apps in the BluixApps catalog.
◇
Jellyfin / Emby / Plex
auth + library check
◈
Sonarr / Radarr
request fulfillment
◆
TMDB
metadata + discovery
▣
Notifications
Discord, Telegram, email, web push, Apprise
▦
API
REST API
▩
Webhooks
fire on request events
▼
Multi-server
track requests across multiple media servers
// Adoption & deployment
Notable users & community
- 4k+ GitHub stars
- Standard request manager for Jellyfin households
- Active r/jellyfin + Discord
- Backed by fallenbagel (fork maintainer)
- Featured in self-hosted Jellyfin guides
What we ship
- Image:
fallenbagel/jellyseerr:latest - Volume:
/opt/jellyseerr/config - Port 5056 exposed (mapped from container 5055 to avoid Overseerr collision)
- Setup wizard supports Jellyfin / Emby / Plex sign-in
- Pairs naturally with same-VPS Jellyfin + Sonarr/Radarr
- HTTPS via Let's Encrypt reverse proxy
- Backup hook covers
/opt/jellyseerr/config
// Tips & operations
Run it properly.
Operational guidance from running this in production — what to lock down, what surprises people.
// PERFORMANCE
Jellyfin auth setup
users sign in via Jellyfin; pre-create accounts in Jellyfin first
// SECURITY
Same Sonarr/Radarr instances
no need for separate from Overseerr setup
// OPERATIONS
Port collision
Jellyseerr uses 5055 by default same as Overseerr; we map to 5056 for co-install
// RELIABILITY
Per-user quotas
request limits prevent abuse
// DEPLOYMENT
Notification setup
push for "your request is ready" matters for adoption
// SCALING
Backup /config
user accounts + permissions
512
// min ram (MB)
2
// min disk (GB)
5056
// access port
http
// protocol
pro
// bluixapps tier
// Alternatives in Media stack
Compare with
Project resources
Official sitedocs.jellyseerr.dev ↗