Scryer Docs

Use these guides to install, configure, and operate Scryer for self-hosted movies, TV series, and anime management.

Start Here

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

• Concepts defines the logical constructs used throughout the app.
• Installation covers Docker, Homebrew, release binaries, and first configuration.
• Getting Started gives you a complete first Docker Compose setup.
• Migrate From Sonarr/Radarr walks through importing multiple existing instances and libraries.
• 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 isn’t the deciding factor.

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

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

These docs are written to help you keep your instance predictable over time. That’s why the emphasis stays on path layout, permission boundaries, reusable configuration, and the screens you use to confirm what Scryer is doing.