What is Prowlarr [Exposed!]?

Prowlarr [Exposed!] removes SSO protection from your ElfHosted Prowlarr instance so external Sonarr, Radarr, Lidarr, or Readarr installations — wherever they're hosted — can pull indexer definitions and search results from your central Prowlarr.

Who needs this?

Anyone running *arr apps outside ElfHosted (or alongside it on a separate hosting provider) who wants a single Prowlarr to manage indexers for everything. Without [Exposed!], external *arr instances can't authenticate against ElfHosted's SSO layer to fetch indexers.

Compatible integrations

• 🔌 External Sonarr, Radarr, Lidarr, Readarr instances
• 🤝 NZBHydra2, Jackett-style aggregators
• 📱 Stremio addons that pull from Prowlarr-managed indexers

Security requirements

You must reset Prowlarr's default API key before subscribing — the platform-default key is shared and unsuitable for public exposure. Generate a fresh key in Prowlarr's settings and paste it into the subscription form during checkout.

Why ElfHosted?

Self-hosting Prowlarr means maintaining indexer definitions, FlareSolverr containers, and Cloudflare-bypass logic yourself — and many private trackers actively block residential IPs. ElfHosted's Prowlarr runs on infrastructure that handles bypass cleanly, and [Exposed!] lets your external *arr stack benefit from it without giving up your existing setup.

FAQ

Will my external *arr apps see all my Prowlarr indexers?
Yes — once authenticated with the API key, external *arr instances see the full indexer list exactly as the ElfHosted-managed ones do.

Does this affect FlareSolverr?
No — FlareSolverr continues to run server-side, transparent to external clients.