A new open-source project called HolyArrs is presenting a single self-hosted application as an alternative to running a collection of separate tools for managing television, films, music, subtitles, indexers and requests. Its developer says the downloadable image is about 15 MB and the service uses roughly 140 MB of memory while idle with a large catalog.
HolyArrs lets a user browse a library-style interface and request a title. The application then searches configured sources, selects a release using user-defined rules, sends the job to an existing downloader and files the completed media in the library. A connected media server detects the item after it arrives. The project does not yet include its own downloader, so users still need software such as qBittorrent or SABnzbd.
The project’s comparison is aimed at households that currently combine Sonarr, Radarr, Lidarr, Bazarr, Prowlarr and Seerr. HolyArrs replaces the coordination layer those six applications provide with one login, port and configuration surface. The developer reports that the six reference container images total 718.2 MB, making the HolyArrs download about 48 times smaller. Those measurements and the memory figure come from the project itself and have not been independently benchmarked in the supplied evidence.
Installation uses a Docker Compose file and supports amd64, arm64 and armv7 systems. After opening port 6262, the first visitor creates the owner account and completes a setup flow for library folders, a downloader and a content source. The documentation warns administrators to create that account immediately because there is no default password and the first person to open an unclaimed instance becomes its owner.
A migration tool can read settings from existing applications or backup archives. Users choose what to import, test the operation and then run the move. HolyArrs says it does not modify the old applications, allowing both setups to operate in parallel. Media files remain where they are, while passwords and keys must be entered again or imported separately. Custom formats, tags and history are not transferred.
The documentation also calls out operational details. A key file in the configuration directory unlocks stored credentials and is not included in normal backups, so administrators must preserve it separately. The container image has no interactive shell. HolyArrs provides its own diagnostic command, and the service creates a backup before storage-format changes during upgrades.
HolyArrs is licensed under AGPL-3.0, with a commercial license offered for closed products. The developer says every installation contacts a project-funded metadata server, meaning the software is self-hosted but not entirely independent of outside infrastructure. For prospective users, the main tradeoff is consolidation: fewer services to configure and troubleshoot, balanced against adopting a young project whose roadmap still includes a built-in downloader and whose resource claims currently come from its maintainer.
