Fetcharr

Fetcharr is a lightweight automation companion for Sonarr, Radarr, Lidarr, and other *arr apps.

  • Automation
  • Downloaders
  • Tools & Utilities
Fetcharr is a lightweight automation companion for Sonarr, Radarr, Lidarr, and other *arr apps. It continuously scans your libraries for missing, wanted, or upgradeable content and triggers active searches automatically to improve media acquisition beyond standard RSS syncing. Designed for self-hosted environments with simple Docker deployment and low resource usage.

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.

61/100 Good

Maintained
68last commit 96 days ago
Popular
51348 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 43 days ago

GitHub stars
348
Open issues
18
Last commit
2026-08-17
Latest release
2.2.1
License
MIT
Activity
stale

Checked 19 days ago - source: GitHub (egg82/fetcharr)

Resources & Compatibility

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

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

First-install notes

  • Add your *arr URLs and API keys first In the Docker Compose startup file, replace the example RADARR_0_URL, SONARR_0_URL, and API_KEY values with your real *arr addresses and secret keys. If these are missing or wrong, Fetcharr can't log in to Radarr/Sonarr/Lidarr/Readarr or find missing media. source
  • Back up config, plugins, and logs Keep the config, plugins, logs, and cache folders on your host by using the provided volume mounts. These hold your saved settings and add-ons, so back them up or you may lose your custom setup. source
  • Tune each *arr library separately You can also tune one *arr library at a time with variables like RADARR_0_SEARCH_INTERVAL or SONARR_0_SKIP_TAGS. That way a movie library can search more often while a TV library stays quiet, without changing every instance. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Fetcharr support plugins?

Yes. Fetcharr offers plugin support for customization and extensibility beyond the base application.

Why does the Fetcharr Docker container need host networking?

Fetcharr finds the box by listening for SSDP announcements on the network. Those broadcasts do not reach Docker's private network, so the container must run with host networking.

What file permission issue is mentioned for a self-hosted *arr stack that includes Fetcharr?

Most problems are from file/folder permissions for the default user. The source notes it is unclear whether each service needs its own media group or user account.

Is there a community forum for Fetcharr?

Fetchforum is a community forum site named Fetchforum.

Answers sourced from furey.github.io, github.com, www.fetchforum.com, www.reddit.com

Community

Collected 53 days ago - public community threads