A desktop monitor displays a Docker-based media library workflow connected to server storage, downloads, and playback.
HolyArrs promises one app in place of the usual media-server stack. XDA Developers' Brian Burgess tried it on a Windows PC with Docker Desktop and came away cautiously impressed, but not ready to switch over fully. His test was a partial, careful trial. It was not a wholesale replacement of Sonarr, Radarr and Lidarr, and the details of that gap matter for anyone thinking of following him.

A desktop monitor displays a Docker-based media library workflow connected to server storage, downloads, and playback. What HolyArrs is​

HolyArrs is a free, open-source app for movies, shows, music, subtitles and requests. It runs as one Docker container in place of Sonarr, Radarr, Lidarr, Prowlarr, Bazarr and Seerr. It is released under the AGPL-3.0 licence.

The "Claude-built" label comes from the AI-assisted development behind it. One community write-up says developer CoderLuii built it with AI coding tools. The same write-up says a notable lesson from the process was that idle RAM crept from 76 MB to 110 MB until measuring every build caught it. Treat that as the developer's account, not independent evidence of quality. An AI-assisted origin says nothing about whether the app is reliable. Your own testing does.

What the XDA test covered​

Burgess ran HolyArrs on a Windows PC through Docker Desktop. He defined the app in a Compose file, started the container from PowerShell, opened the web interface and created a local owner account. His media lived on a NAS, so he also added an authenticated network-share connection to Docker. Then he pointed HolyArrs at his music, movie and TV folders in the setup wizard.

Here is what he found:

  • Read-only first. He started with the NAS connection read-only so the tool could look but not touch.
  • Scan results were mixed. On a movie library already named in a way Plex and Jellyfin recognise, the scan flagged some titles as missing or uncertain, and he considered some of its matches incorrect. He called it overly cautious. He still found it easy to look up and verify movies, shows and albums.
  • A small adoption test. He switched the share to read/write and let HolyArrs adopt four movies, rather than handing over the whole collection.
  • Useful interface features. He could sort by size, quality and series progress, and there is a release calendar. Household members can request titles for an admin to approve. The library view is kept separate from discovery pages.
  • Integrations skipped. He left Prowlarr/Jackett and Plex/Jellyfin/Emby connections for later.
  • The old apps stay. He says he will keep the other tools running for now.

What the test did not show is an end-to-end automated download workflow. It was mainly a library scan and a small adoption trial.

One app, but not zero dependencies​

"One app" needs a caveat. HolyArrs' own comparison page says it does not download by itself. It hands each release to a downloader, and the page names qBittorrent, Transmission, Deluge, SABnzbd or NZBGet among the options. The project's documentation also lists rTorrent and aria2. Sources use Torznab, Newznab or RSS feeds, and a site with no feed of its own needs a bridge such as Prowlarr or Jackett. Plex, Jellyfin and Emby stay as your playback servers, and HolyArrs notifies them after imports, deletions and renames.

The project is also candid about its age. The comparison page says the first release came in November 2026 and advises testing it with your own setup before relying on it. It also lists other gaps: no plugin system yet, subtitle search held back in the current release, and no support for helpers such as Recyclarr, Maintainerr and Cleanuparr.

Docker Desktop on Windows: what to get right​

The install guide has several points that matter on a Windows machine:

  1. Use a named volume for /config. The guide says Docker Desktop shares host folders through a layer where database file locks are not safe. HolyArrs refuses a /config there. Media folders can stay as host folders.
  2. Create the owner account immediately. The web interface defaults to port 6262. There is no default password, and whoever opens a fresh install first becomes the owner.
  3. Don't forward port 6262 on your router. The docs recommend a VPN such as Tailscale, or a reverse proxy with HTTPS.
  4. Back up the master key separately. HolyArrs encrypts stored passwords, keys and tokens with /config/holyarrs.key. Backups don't contain it, and a restore with a different key is refused. The guide suggests the Download key kit option under Settings > Backups.
  5. Give the container write access. HolyArrs never changes ownership of your media or download folders, and read access isn't enough because it creates folders and moves files. This is why Burgess's read-only start was a sensible way to test, and also why he had to loosen it before adoption could work. The docs also note that some storage can't change owners, such as SMB or NFS with root squash. In that case you must make the config folder writable by hand.

Storage layout and NAS copies​

The docs favour a single data folder mounted at /data, with downloads and library folders inside it. They say finished downloads then arrive as a hardlink or move, with no extra space used, provided it is one filesystem on the host. Separate /movies, /tv, /music and /downloads mounts work, but every import is then a full copy because each is its own mount inside the container. The docs add that separate NAS shares or datasets under one folder still copy.

That is the layout Burgess's setup resembles, with a NAS share as the library. Large media files get copied rather than moved, which costs time and disk space. It's worth planning before you enable automated imports.

Migration: available, but not what XDA tested​

HolyArrs has an importer that reads your existing apps by address and API key. The docs say it reads them without changing them or moving media files, and you can undo an import. The steps are:

  1. Open Settings > Import from other apps and click Add an app.
  2. Pick the app, enter its address and API key, and click Test. You should see the app's name and version.
  3. Map old folders to HolyArrs library folders under "What to import".
  4. Check the counts on the "Before you import" sheet, then confirm.

For Sonarr and Radarr, the docs list titles, folders, files, quality profiles (matched to the nearest Pick rules preset), exclusions, indexers and download clients, remote path mappings and naming as coming across. Sources and downloaders arrive paused, and keys and passwords never come over, so you must retype them and resume each item. Imported downloaders use their own holyarrs category so they don't pick up downloads the old apps started.

The documented list of what stays behind is long:

  • custom formats that no profile scores
  • tag-scoped wait rules
  • release word rules
  • language profiles
  • tags
  • some list types
  • history

For Lidarr, artists are matched by MusicBrainz ID with files left in place. Metadata profiles, music import lists, custom formats, release word rules and tags stay behind.

The XDA piece describes scanning the NAS library and reviewing matches, not importing from the old apps. So the importer's behaviour here comes from the project's documentation, not Burgess's testing.

What other coverage says​

Other coverage is consistent on the main points. A write-up of the project's Show HN launch says the migration changes nothing in the old apps and that a built-in downloader is planned for later. A Synology guide from Marius Hosting says you can keep the Arrs running alongside HolyArrs while you test it. A third-party SSD Nodes migration guide says the docs describe nothing for a Lidarr side of music requests, which is relevant if you rely on a Seerr-style request flow for music.

The size and memory figures are the developer's own measurements, not independent benchmarks. The comparison page reports a 16.1 MB compressed image versus 652.6 MB for the six apps combined, measured on November 13, 2026. It also reports about 95 MB of idle RAM on a fresh install. One summary of the earlier launch cites about 140 MiB with a 10,000-title library, again by the author's own measurement. Your memory use will depend on your library.

Should you try it?​

It looks reasonable to try if you already run the Arr stack on Windows with Docker Desktop and want to cut the number of dashboards. Run it beside the existing apps, as Burgess did, and keep these points in mind:

  • Start with read-only access, then widen to read/write for a small batch.
  • Expect to review matches even on a well-named library.
  • Keep Sonarr, Radarr and Lidarr until HolyArrs has handled a few real download cycles with your downloader and indexers.
  • Check the "stays behind" lists before you retire any old app, especially if you lean on custom formats, tags or history.
  • Keep the master key and a backup of your configuration somewhere safe.

The cautious verdict from the XDA test is the right one. HolyArrs consolidates the interface well, but trust in an app that can move your files has to be earned over time. This one is days old.

 

References

  1. I replaced Sonarr, Radarr, and Lidarr with a single Claude-built app, and it changed how I manage my media server XDA 2026-11-19T16:30:24+00:00
  2. HolyArrs vs Sonarr, Radarr, Lidarr, Prowlarr, Bazarr, Seerr holyarrs.com
  3. Lidarr, Bazarr and Prowlarr | HolyArrs Docs docs.holyarrs.com