Overview

Prowlarr is an indexer manager and proxy for the *arr media stack. It keeps the list of torrent trackers and Usenet indexers in one place, tests them, and pushes them automatically to Sonarr, Radarr, Lidarr and Readarr instead of you maintaining the same indexer four times in four interfaces. It is built on the same .NET and React base as the rest of the Servarr family, licensed GPL-3.0, and ships as a single container or native package.

Every indexer is exposed through the Newznab and Torznab APIs, so applications that never heard of Prowlarr can still consume it as a normal indexer. On a fresh install the catalogue held 658 pre-written indexer definitions.

Key Features

• One indexer list for the whole stack: add a tracker or Usenet indexer once and let Prowlarr sync it to Sonarr, Radarr, Lidarr and Readarr through the Apps settings, including per-app category mappings.
• Hundreds of built-in definitions: public and private torrent trackers plus Usenet indexers are maintained centrally — the catalogue on a clean install listed 658 indexer definitions, searchable and filterable by protocol, language, privacy and category.
• Automatic sync and testing: indexers are tested on a schedule, failures surface in the UI, and app syncs push additions, edits and removals without touching each downstream app by hand.
• Newznab and Torznab endpoints: anything that speaks the standard indexer API can use Prowlarr directly, with per-indexer API paths and a server-wide API key.
• Indexer proxies: optional HTTP and SOCKS5 proxies per indexer, plus FlareSolverr integration for trackers that sit behind a Cloudflare browser check.
• Search and history: a manual search page that queries one indexer or all of them at once, and a history view of queries, grabs and failures for diagnosing a tracker that stopped returning results.
• Statistics: per-indexer query and grab counters, average response time and failure rate, which makes a slow or failing tracker obvious before downloads start disappearing.
• Deployment options: official container image, Windows, Linux and macOS builds, and the usual Servarr layout — a config directory you can back up and move between hosts.

Why Use Prowlarr

Without it, every indexer has to be entered into every downloader: four apps, dozens of trackers, and a passphrase change on a private site means four edits. Prowlarr inverts that — the indexers live in one database, the apps subscribe to it, and a tracker that dies is replaced in one place. The proxy and FlareSolverr support also means the odd Cloudflare-protected tracker keeps working without a separate scraping stack, and the statistics page turns “downloads are slow” into a measurable per-indexer number rather than a guess.

Use Cases

• A full *arr stack: the standard companion to Sonarr, Radarr, Lidarr and Readarr for anyone running the Servarr suite in Docker.
• Managing private trackers: keep credentials, categories and per-indexer proxies in one place, with passkey changes applied once and synced out.
• Usenet and torrent side by side: both protocols are managed in the same list, so a hybrid setup does not need two tools.
• Diagnosing dead indexers: when a download job stops finding releases, the test-all and statistics views show which indexer broke and when.