Throttlearr

Throttlearr is a queue limiter that sits between Sonarr, Radarr, Lidarr, and Readarr and SABnzbd to prevent download floods.

  • Downloaders
  • Tools & Utilities
Throttlearr is a queue limiter that sits between Sonarr, Radarr, Lidarr, and Readarr and SABnzbd to prevent download floods. It keeps grabbed releases in its own queue and sends them to the real SABnzbd only when configured limits for active jobs, remaining download size, adds per hour, allowed hours, and free disk space are satisfied. Held releases stay queued in the collection apps, reducing timeouts, duplicate grabs, and blocklists. It also inspects the inside of each download before it reaches SABnzbd and reports releases that contain only programs, repair data, or sample clips as failed. Users with large backlogs can keep SABnzbd stable without manually pausing Sonarr or Radarr.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

42/100 Fair

Maintained
72last commit 5 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-11-16
License
MIT
Activity
rising

Checked 5 days ago - source: GitHub (aon082910/throttlearr)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 5 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Point collection apps to Throttlearr Set the Sonarr, Radarr, Lidarr, and Readarr SABnzbd connection to Throttlearr's host, port, and API key instead of the direct SABnzbd server. source
  • Bypass Throttlearr Use Throttlearr's fail-open switch to pass all downloads straight through when you need to bypass the limiter temporarily. source

Fetched 5 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What do I change in Sonarr, Radarr, Lidarr, or Readarr to start using Throttlearr?

Point the download client at Throttlearr instead of SABnzbd and change only the host, port, and API key.

Do the *arr apps know when Throttlearr is holding a grabbed release?

Held jobs show as queued, so the apps do not time out, re-grab, or blocklist them.

Can Throttlearr stop a large missing-search from overwhelming SABnzbd?

You can set limits such as at most N jobs in SABnzbd, a cap on gigabytes still to download, and a limit on adds per hour.

Can I keep downloads from running outside certain hours or filling the disk?

Yes, you can set allowed hours and a free-disk floor before Throttlearr hands jobs to the real SABnzbd.

Answers sourced from github.com

Community

No community discussions collected yet.