Skip to content

Scryer vs. Profilarr

Profilarr keeps Radarr and Sonarr custom formats and quality profiles in sync with a curated, git-backed database. It solves a real problem: maintaining dozens of custom formats by hand is error-prone. Scryer removes the problem instead of automating it.

ProfilarrScryer
DeploymentSeparate app pushing to each *arrNothing extra
Source of truthCommunity database, pulled over gitTRaSH Guides data compiled into each Scryer release
Unit of preferenceCustom formats, each with a per-profile scoreA scoring persona applied to release-group tiers, sources, codecs, HDR, and size
Local exceptionsEdit or fork the synced formatsScoring overrides on the profile, plus Rego custom rules
BundlesProfile bundles per use caseBalanced, Audiophile, Efficient, and Compatible personas; rule packs as plugins
UpdatesProfilarr sync runUpgrade Scryer

Pick a persona, not a stack of formats. A persona sets roughly fifty weights at once. Most libraries are done after choosing one per facet or per library.

Overrides instead of forks. Want lossless audio without the rest of Audiophile, or to block Dolby Vision without a fallback layer? Those are switches on the quality profile, not edited formats that drift from upstream.

Rules where formats run out. Anything a custom format cannot express, such as combining several conditions with real boolean logic or reading anime-specific fields, is a short Rego rule. Custom Rules Vs Custom Formats ports the common ones.

Updates ride along with releases. There is no sync action to schedule or break. The trade-off is that a TRaSH change reaches you at your next Scryer upgrade rather than on Profilarr’s cadence.

What Profilarr Still Does That Scryer Does Not

Section titled “What Profilarr Still Does That Scryer Does Not”
  • Profilarr manages formats for Radarr and Sonarr instances you keep running.
  • Profilarr exposes the individual upstream rules for editing. Scryer’s bundled data is not editable; use overrides and rules for exceptions.