HolyArrs
HolyArrs is a self-hosted web app for finding, requesting and managing your shows, movies and music in one place instead of running Sonarr, Radarr, Lidarr,…
Platform availability
Available on 3 of 10 platforms
- Unraid
- TrueNAS
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
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.
72/100 Good
- Maintained
- 72last commit 9 days ago
- Popular
- 59842 GitHub stars
- Easy to install
- 553 install platforms, install notes, Docker image
- Light to run
- 10070 MB minimum RAM, runs on ARM
- Security check
- 82no serious findings, CI, tests, new single-developer project, OpenSSF Scorecard 7/10
Availability: platform listings confirmed today
- GitHub stars
- 842
- Open issues
- 108
- Last commit
- 2026-11-12
- Latest release
- 1.0.19
- License
- AGPL-3.0
- Activity
- rising
Checked 10 days ago - source: GitHub (HolyArrs/HolyArrs)
Resources & Compatibility
Minimum requirements: 70 MB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 10 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start the app and check it is healthy Run `docker compose up -d`, then `docker compose ps`, to start HolyArrs and check its status. If it does not show healthy, the app is not ready yet, so check the container before using the web page. source
- Use port 6262 for the first-run wizard After starting the app, open http://your-server:6262 in a browser, replacing your-server with your machine's address. The first visitor becomes the owner, so make sure you are the first one to reach that page or you may be locked out. source
- Copy the old master key before first start If you are using an existing config folder, run `docker compose create` first and copy the old master key into the new config. That key is needed to open your old data, and skipping it can leave your previous setup unreadable. source
- Unraid volume placement On Unraid, keep the /config volume on a direct-pool path such as /mnt/cache/appdata/holyarrs rather than a user share like /mnt/user, and for hardlinks map one share that holds both your downloads and your library folders. source
Fetched 10 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which host port should HolyArrs use?
The Docker setup publishes port 6262, and you open that port in your browser after the container starts.
Which Docker volumes are shown in the install example?
Bind a local path to /config and map your media and download locations to /movies, /tv, /music, and /downloads.
Where can I find migration help for HolyArrs?
The docs include guidance for installing HolyArrs, moving over from your old apps, or looking up a setting.
Answers sourced from docs.holyarrs.com, holyarrs.com
Community
- Reddit (reddit)
Collected 10 days ago - public community threads
