Jellyseerr

App in the BluixApps catalog

What it is

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.

What it's for

  • Jellyfin household request portal — friends/family request content
  • 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

  • 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

Why teams pick Jellyseerr over 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

  • 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

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

Tips & operations

  • Jellyfin auth setup — users sign in via Jellyfin; pre-create accounts in Jellyfin first
  • Same Sonarr/Radarr instances — no need for separate from Overseerr setup
  • Port collision — Jellyseerr uses 5055 by default same as Overseerr; we map to 5056 for co-install
  • Per-user quotas — request limits prevent abuse
  • Notification setup — push for "your request is ready" matters for adoption
  • Backup /config — user accounts + permissions

What we ship in BluixApps

  • 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
Read this app's deep dive on bluix.app ↗

Get this app — pick a BluixApps plan

Same catalog. Scaling tenant isolation, white-label and support tier.

TierTenantsCatalogSupportWhite-labelMonthly
Stacks119 curated stacksStandard$19/moDetailDeploy
Starter10Full catalogStandard+$15–25/mo$49/moDetailDeploy
Pro25Full catalogPriority bugfix+$15–25/mo$149/moDetailDeploy
Growth100Full catalogPriority bugfix+$15–25/mo$349/moDetailDeploy
Scale500Full catalog7-day window+$15–25/mo$799/moDetailDeploy
EnterpriseUnlimitedFull catalogPriority 7-dayBundled$1,499/moDetailDeploy

Powered by WHMCompleteSolution