Skip to content
scryer media docs

Scryer Docs

Scryer is a self-hosted media management application for movies, TV series, and anime.

Start Here

Section titled “Start Here”
  • Concepts defines the logical constructs used throughout the app.
  • Installation covers Docker, Homebrew, release binaries, and first configuration.
  • Release Notes tracks milestone-level changes and migrations. Patch-level detail stays in GitHub releases.
  • Library Layout explains paths, media roots, and download staging.
  • Permissions and Navigation explains why some sidebar items may be hidden.
  • Global Search explains the app-wide title search flow, including how to add new catalog entries.
  • Plugins explains plugin kinds, support tiers, install sources, and development-oriented manual installs.
  • Compare With Sonarr/Radarr explains why Scryer can be more compelling than a split *arr setup even when RAM is not the deciding factor.

If you are bringing up a new instance, read those pages in that order. If Scryer is already running and you are trying to understand a screen in the UI, jump straight to the matching section in the left-hand navigation below.

App Navigation

Section titled “App Navigation”

The rest of the docs mirror Scryer’s current left-hand navigation:

  • Architecture covers internal design pages such as the domain event model and release parsing architecture.
  • Movies, Series, and Anime cover catalog browsing, imports, and per-facet settings.
  • Activity covers operational events, manual import work, and activity history.
  • Calendar covers scheduled episodes and title navigation.
  • Wanted covers missing, pending, and cutoff-unmet work.
  • Settings covers global configuration.
  • System covers health and background jobs.

Operator Stance

Section titled “Operator Stance”

Scryer is a control plane for an existing, lawful media environment. Provider pages describe the fields Scryer needs to store, validate, and use configured connections.

The docs are written for operators who need to keep the instance predictable over time. That means the emphasis stays on path layout, permission boundaries, reusable configuration, and the screens the user uses to confirm what Scryer is doing.