Skip to content

Scryer vs. Seerr

Seerr (Overseerr, Jellyseerr) is a request portal. Users sign in with Plex or Jellyfin, browse, and request; Seerr then calls Sonarr or Radarr to add the title. Scryer folds the portal into the manager.

SeerrScryer
DeploymentSeparate app with its own database and usersPart of Scryer
Sign-inPlex, Jellyfin, Emby, or local accountsSame, through media server connections, plus passkeys and MFA
User provisioningImport users from the media serverAuto-add verified media server users with default permissions and library grants
Request scopePer user, with 4K as a separate serverPer library: request and autoApproveRequests permissions, requestable profiles per library
ApprovalSeerr queue, then pushed to *arrScryer queue; approver picks final profile and monitor type
Status trackingSeerr polls *arr for availabilitySame catalog, so status is immediate
DiscoveryTrending and recommendationsDiscovery pages with request actions

Libraries replace server pairs. In Seerr, offering 1080p and 4K means two Radarr servers and per-user 4K permission. In Scryer, a “Movies 4K” library with its own roots, profiles, and request grants does the same job.

One permission model. The person who can request in a library is defined in the same place as the person who can manage it. Media server users inherit a connection’s default grants, so onboarding a household is a single switch.

No sync lag. Seerr must poll to learn a request was fulfilled. Scryer’s request and the imported file are the same record, so requesters see progress as it happens.

What Seerr Still Does That Scryer Does Not

Section titled “What Seerr Still Does That Scryer Does Not”
  • Seerr runs in front of any Sonarr or Radarr. Scryer requests only target Scryer libraries.
  • Seerr has issue reporting and per-user request quotas. Scryer approvals are manual or auto-approved per library, without quotas.