Scryer Vs Sonarr And Radarr

RAM efficiency is nice, but it is not the only reason to care about Scryer.

Scryer provides one system for movies, series, and anime with:

Sonarr and Radarr are mature tools with a familiar split-app model. Scryer takes a different path:

Fewer separate moving parts
Richer shared-library controls
More of the advanced behavior built into the core model instead of layered on around it

Core Product Features

Category	Feature	Scryer	Sonarr / Radarr
Library Management	Monitor and track titles	✅	✅
Library Management	Automatic RSS monitoring and grabs	✅	✅
Library Management	Interactive search and manual grabs	✅	✅
Library Management	Completed download handling and import	✅	✅
Library Management	Manual import tools	✅	✅
Library Management	Import lists / watchlist sync	❌	✅
Library Management	Import list exclusions	❌	✅
Library Management	Rename and organize library files	✅	✅
Media Requests	Request movies, series, and anime from the app	✅	❌
Media Requests	Approval queue, rejection, cancellation, and request history	✅	❌
Media Requests	Per-library request permissions, quality defaults, and auto-approval	✅	❌
Quality & Decisioning	Quality profiles	✅	✅
Quality & Decisioning	Automatic upgrades to better releases	✅	✅
Quality & Decisioning	Advanced release decision rules	✅	✅
Quality & Decisioning	User based rules	✅	✅
Quality & Decisioning	Delay profiles / delayed grabbing	✅	✅
Automation	Post-processing scripts	✅	✅
Automation	Webhook / notification events	✅	✅
Operations	Activity and history views	✅	✅
Operations	Wanted / missing / unmet views	✅	✅
Scope	Movies, series, anime, and subtitles in one app	✅	❌
Scope	Dedicated subtitle management	✅	❌
Scope	Multiple libraries per media type	✅	❌
Scope	Per-user permissions and library boundaries	✅	❌
Extensibility	Plugin-based provider ecosystem	✅	❌

Media Requests

Scryer includes media requests as part of the same application that manages titles, libraries, permissions, quality profiles, and notifications.

Users can request movies, series, and anime from Scryer’s search flow, while operators keep review and approval inside Scryer instead of wiring a separate request portal into Sonarr and Radarr. Request behavior follows Scryer’s library boundaries: each library can expose its own requestable quality profiles, defaults, requester access, and auto-approval behavior.

Sonarr and Radarr can still be excellent acquisition backends for request-oriented stacks, but they normally depend on a sidecar such as Seerr for the request UI and approval workflow. In Scryer, that workflow is native.

Integration Matrix

Download Clients

Bucket	Scryer	Sonarr / Radarr
Aria2	Beta	✅
Deluge	Beta	✅
Download Station	Beta	✅
Flood	Beta	✅
Freebox Download	Beta	✅
Hadouken	Beta	✅
NZBGet	✅	✅
NZBVortex	Beta	✅
Pneumatic	Beta	✅
qBittorrent	✅	✅
RQbit	Beta	✅
SABnzbd	✅	✅
Torrent Blackhole	Beta	✅
Transmission	Beta	✅
Tribler	Beta	✅
Usenet Blackhole	Beta	✅
Vuze	❌	✅
rTorrent	Beta	✅
uTorrent	Beta	✅

Indexers & Search

Bucket	Scryer	Sonarr / Radarr
AniNZB	✅	Via Newznab
BroadcastheNet	Beta	✅
DogNZB	✅	Via Newznab
Fanzub	Beta	✅
FileList	Beta	✅
HDBits	Beta	✅
IPTorrents	Beta	✅
Newznab	✅	✅
NZBGeek	✅	Via Newznab
Nyaa	Beta	✅
Prowlarr	✅	✅
Torrent RSS	✅	✅
TorrentLeech	Beta	✅
Torznab	✅	✅

Notifications & Automation

Bucket	Scryer	Sonarr / Radarr
Apprise	Beta	✅
Custom Script	Beta	✅
Discord	Beta	✅
Email	✅	✅
Gotify	Beta	✅
Jellyfin	✅	❌
Join	Beta	✅
Mailgun	Beta	✅
MediaBrowser / Emby	Beta	✅
Notifiarr	Beta	✅
ntfy	Beta	✅
Plex	Beta	✅
Prowl	Beta	✅
Pushbullet	Beta	✅
Pushcut	Beta	✅
Pushover	Beta	✅
SendGrid	Beta	✅
Signal	Beta	✅
Simplepush	Beta	✅
Slack	Beta	✅
Synology	Beta	✅
Telegram	Beta	✅
Trakt	Beta	✅
Twitter / X	Beta	✅
Webhook	✅	✅
XBMC / Kodi	Beta	✅

Subtitles

Bucket	Scryer	Sonarr / Radarr	Bazarr
Enhanced subtitle sync	Beta	❌	✅
Jimaku	✅	❌	✅
OpenSubtitles	✅	❌	✅
Subdl	✅	❌	✅
Other subtitle providers	❌	❌	✅

The Bigger Difference: Multi-User, Multi-Library From The Start

Instead of treating movies, series, and anime as single flat buckets, Scryer supports multiple libraries under each media type. Each library can have its own root folders, defaults, and access boundaries, while still living inside one coherent application.

That means real household and shared-server scenarios can be modeled directly:

Kids
Anime Movies
Rated R+
Mainline TV

Each of those can point at different root folders. Users can then be assigned to the libraries they should be able to see and operate on.

Deeply Multilingual, Not Just A Translated UI

Scryer’s multilingual work goes deeper than interface text.

The content model itself is built to work with multilingual metadata, which matters when operating a library for users with different language preferences, following anime titles with multiple naming conventions, or wanting better control over how titles are represented across a collection.

Anime Is A First-Class Media Type

Anime is not treated as an awkward variant of TV.

Scryer has dedicated anime behavior, including filler/recap awareness and canon-movie handling. That makes it better suited to series where “what counts”, “what should be watched”, and “where does this movie fit” are part of the real management problem.

For libraries that include anime beyond occasional mainstream titles, this is one of the clearest places where Scryer feels purpose-built instead of merely compatible.

Release Parsing That Understands Context Better

Scryer uses a different parsing approach than the traditional *arr stack: a contextual, beam-style parser that is better at turning release names into structured data.

That matters because downstream decisions depend on what the parser can reliably extract:

Quality and source
Release group
Edition and cut metadata
Language and subtitle hints
Episode and season structure
Anime-specific details

For a detailed breakdown of the parser difference, including a side-by-side diagram and the latest benchmark table, see Context-Free Vs Context-Aware Release Parsing.

Faster Interactive Indexer Search

Parsing quality also shows up in the feel of the UI.

When an operator runs an interactive search, Scryer is much faster at turning large release result sets into something actionable. The difference is especially noticeable for long-running series and anime, where a search can surface a lot of noisy candidates that still need to be parsed and scored before they become useful.

Subtitles Are Built In

Subtitle management is part of the product, not an afterthought.

Scryer handles subtitle workflows inside the same application instead of pushing operators toward a separate sidecar app and another set of credentials, policies, and operational surfaces. If subtitles matter in the environment, that reduction in moving parts is a real quality-of-life improvement.

Better Completion For Torrent Downloads

Completed-download import is another place where Scryer aims to finish the job instead of stopping early.

In Sonarr and Radarr, completed-download import operates on discovered media files, and their cleanup logic explicitly treats large .rar files as leftover manual cleanup instead of importable payload. Scryer can complete imports when the media is still inside a supported archive, including .rar, and move the finished media safely into the library.

For torrent flows that leave content archived, this removes a whole class of manual cleanup and “why did this not import?” troubleshooting.

A Real Plugin System

Scryer ships a robust plugin system so the ecosystem can grow without forcing every feature through the core distribution path. Community contribution gets easier because new capabilities do not always require a core merge, and operators can load the pieces they actually use instead of carrying every provider integration by default.

This is a better fit for a media stack where different operators want different indexers, subtitle providers, download clients, and notification integrations.

Simpler Release Rules Without Giving Up Power

Sonarr and Radarr rely heavily on Custom Formats to encode nuanced preference logic such as release-group boosting and the more advanced policies collected by communities like TRaSH Guides.

Scryer takes a different approach with Personas.

Personas were designed by looking at what operators were actually trying to achieve with Custom Formats and collapsing the most common intent into four simple buckets. That gives most users a much easier starting point without forcing them to hand-build an intricate scoring model first.

When deeper control is needed, Scryer still provides a powerful custom rules engine. The goal is not to remove power — the goal is to make the common path much simpler, while still letting advanced operators go far beyond Custom Formats.

Library — multiple libraries per media type with separate roots and permissions enable the multi-user boundary model described on this page
Permissions — access grants that determine which libraries and operations each user can reach
Subtitle Provider — a configured subtitle source managed inside Scryer without a separate sidecar app
Plugin — a package that adds provider capabilities; keeps the core lean while enabling ecosystem growth
Rules — conditions that shape routing and release decisions; the engine behind Personas
Context-Free Vs Context-Aware Release Parsing — detailed breakdown of Scryer’s beam-style parser versus traditional context-free parsing
Concepts — definitions for all logical constructs used throughout the app
Subtitles — where subtitle provider instances are configured
Plugins — plugin kinds, support tiers, install sources, and development-oriented manual installs
Rules — where rule sets are created and managed
Users — where user accounts and library access grants are managed