# Rangarr

Rangarr is a lightweight orchestration service that automates and staggers media searches across multiple *arr instances (Radarr, Sonarr, Lidarr). It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/1529/rangarr

## Description

Rangarr is a lightweight orchestration service that automates and staggers media searches across multiple *arr instances (Radarr, Sonarr, Lidarr). It keeps your library complete without overwhelming your indexers or API limits by spacing out search requests to avoid "thundering herd" bursts. From a single service you can manage all your *arr instances, interleave searches between missing items and upgrades, and weight specific instances — all with no telemetry, as Rangarr only communicates with the *arr instances you configure.

## Platform availability

Available on 2 of 10 platforms: Unraid, Any server.

## Health score

65/100 (Good), based on 5 of 5 factors.
- Maintained: 87 (last commit 42 days ago)
- Popular: 48 (265 GitHub stars)
- Easy to install: 45 (2 install platforms, install notes, Docker image)
- Light to run: 20 (16 GB minimum RAM, runs on ARM)
- Security check: 95 (no serious findings, CI, tests)

## Links

- Docker Hub: https://hub.docker.com/r/judochinx/rangarr
- Unraid: https://ca.unraid.net/apps/rangarr-0xm57nm1bknjmm?q=Rangarr
- GitHub: https://github.com/JudoChinX/rangarr

## Common questions

### How should Rangarr be configured?

The default template uses environment variables. You can also use a config.yaml by mapping the /app/ path.

### How does Rangarr reduce search pressure on indexers?

It staggers and rate-limits searches across the connected *arr apps.

### Does Rangarr communicate with services other than my *arr instances?

It has no telemetry and only communicates with the *arr instances you configure.

---
Source: Our Local Host (https://ourlocalhost.com/app/1529/rangarr), the self-hosted and open-source app directory.
