Indexer centralization
manage 10+ indexers in one place
// official site: prowlarr.com ↗
MEDIA STACK · PRO TIER
Prowlarrpro
Prowlarr is the centralized indexer manager for the *Arr stack — configure your indexers (NZB, torrent, Usenet) once in Prowlarr, push the config to Sonarr/Radarr/Lidarr/Readarr automatically. Modern replacement for Jackett with native protocol support.
// What it is
A closer look.
Prowlarr is the centralized indexer manager for the *Arr stack — configure your indexers (NZB, torrent, Usenet) once in Prowlarr, push the config to Sonarr/Radarr/Lidarr/Readarr automatically. Modern replacement for Jackett with native protocol support.
If you have multiple *Arr apps and configured indexers in each manually, Prowlarr deletes that pain.
// Use cases
What it's for.
Concrete scenarios where teams pick Prowlarr over the SaaS alternative.
Multi-app push
same indexer config across Sonarr + Radarr + Lidarr + Readarr
Indexer health monitoring
alerts on indexer failures
Search testing
verify indexer responses without grabbing
Stats + history
track grab success rates per indexer
// Who it's for
Built for these teams.
If your team profile matches one of these, Prowlarr is a strong fit out of the box.
Self-hosted media stack operators
running 2+ *Arr apps
Indexer-heavy users
with private tracker memberships
Power users
managing 5-20 indexers across protocols
Multi-user households
with shared *Arr stack
*Arr-stack newcomers
wanting the modern setup
// Differentiators
Why teams pick Prowlarr.
When evaluating self-hosted options for this category, here are the dimensions on which Prowlarr consistently lands above the alternatives.
- ✓GPLv3 — fully open
- ✓Native *Arr protocol — auto-push config (Jackett requires manual sync)
- ✓Multi-app architecture — designed for multi-*Arr deployments
- ✓Modern UI — same as Sonarr v4+ visually
- ✓Active development — frequent releases
- ✓Replaces Jackett — clean migration path
// Integrations
Connects to.
The stack you'll plug Prowlarr into — services, protocols, and adjacent apps in the BluixApps catalog.
◇
Sonarr v4+ / Radarr v4+ / Lidarr / Readarr
primary push targets
◈
Indexers
NZB (Newznab), torrent (Torznab), Usenet, FlareSolverr-protected
◆
FlareSolverr
bypass Cloudflare on protected indexers
▣
Notifications
Discord, Telegram, custom webhook
▦
API
REST API for programmatic indexer mgmt
▩
Indexer health
automatic disable on persistent failure
▼
Categories
auto-mapped to *Arr apps based on type
// Adoption & deployment
Notable users & community
- 5k+ GitHub stars
- Standard indexer manager in modern self-hosted media stacks
- Active community on r/prowlarr + Discord
- LinuxServer.io Docker image maintained
- Featured in every modern *Arr-stack guide
What we ship
- LinuxServer.io image:
lscr.io/linuxserver/prowlarr:latest - Volume:
/opt/prowlarr/config - PUID/PGID 1000 default
- Port 9696 exposed
- Pairs naturally with all *Arr apps on same VPS
- HTTPS via Let's Encrypt reverse proxy
- Backup hook covers
/opt/prowlarr/config
// Tips & operations
Run it properly.
Operational guidance from running this in production — what to lock down, what surprises people.
// PERFORMANCE
Migrate from Jackett
Prowlarr has Jackett import tool; one-time migration
// SECURITY
App URLs for push
use http://sonarr:8989 if all on same Docker network
// OPERATIONS
API keys for each *Arr app
needed to register them with Prowlarr
// RELIABILITY
Categories matter
set per-indexer; Prowlarr maps them to *Arr apps
// DEPLOYMENT
FlareSolverr for Cloudflare
install separately if any indexer needs it
// SCALING
Backup /config
indexer configs + API keys
256
// min ram (MB)
1
// min disk (GB)
9696
// access port
http
// protocol
pro
// bluixapps tier
// Alternatives in Media stack
Compare with
Project resources
Official siteprowlarr.com ↗