What is rangarr?

A lightweight daemon that coordinates media searches across the major *arr applications. It keeps libraries complete while respecting indexer limits by managing many instances from one place, allocating search slots globally, interleaving instances to spread load, staggering requests to avoid thundering herds, balancing missing and upgrade searches, weighting instances by priority, supporting season packs for TV with fallback for airing shows, running missing and upgrade searches on separate schedules, skipping recently searched items with configurable windows, finding custom format score gaps that *arr misses, filtering by tags, limiting searches to specific hours, and configuring via YAML with env expansion or pure environment variables. Runs as a non-root Docker container on a distroless base, talks only to your configured *arr instances, has no telemetry or external calls, no web UI, and operates as a scheduled background daemon.

Should you self-host rangarr?

rangarr scores 47/100 on selfhost.directory (how scoring works) and ranks #85 of 142 in Media Management. It has 265 GitHub stars.

It shipped 12 stable releases in the past year. The latest, v0.11.0, came out on 19 September 2026. New versions land roughly every 3 days.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is MIT-licensed and written mostly in Python.

Its closest alternative on selfhost.directory is Sonarr (81/100, 17 471 stars). It scores higher overall, so compare the two before you pick. See rangarr vs Sonarr side by side.