Quick Answer: A Sonarr Radarr alternative like HolyArrs replaces six self-hosted apps with one: Sonarr, Radarr, Lidarr, Prowlarr, Bazarr and Overseerr. The project's README reports a 14.9 MB amd64 download, about 140 MiB of idle RAM with 10,000 titles, and one login on port 6262. Some features are explicitly deferred past 1.0, so check the gaps before you switch.
Most people searching for a Sonarr Radarr alternative aren't unhappy with the apps themselves. They're tired of running six of them. Each one has its own login, its own port, its own update cycle and its own API key, and every key has to be copied into the others by hand. HolyArrs is a self-hosted app that tries to collapse that stack into one. Here's what it does, what it doesn't, and how to decide whether it fits your server.
Why six apps turn into a debugging problem
The usual advice is that the *arr stack is modular, and modularity is a feature. Separate apps fail independently, and you can swap one out without touching the others. That's true. But the cost of modularity rarely shows up on the spec sheet. It shows up at 11 p.m. when a show won't land.
Take a typical failure. A season is marked as missing. The cause could be a dead indexer in Prowlarr, a missing quality profile in Sonarr, a download client that rejected the grab, or a stale API key that Sonarr quietly stopped using. You check four or five places before you find the one line that matters. The problem isn't the apps. It's that nothing ties the whole chain together.
HolyArrs takes the opposite bet: one login, one port, one place to look. That's the core pitch in the project's README, and it's the right place to start if your main complaint is coordination rather than features.
What the numbers actually show
The project publishes a comparison of compressed registry downloads for the linuxserver.io images on amd64. Here's the relevant slice:
| App | Download (amd64) | Logins | Web port |
|---|---|---|---|
| Sonarr | 87.9 MB | 1 | 1 |
| Radarr | 91.0 MB | 1 | 1 |
| Bazarr | 156.4 MB | 1 | 1 |
| Overseerr | 180.8 MB | 1 | 1 |
| HolyArrs | 14.9 MB | 1 | 1 (port 6262) |
The six apps together come to 718.2 MB, and HolyArrs is about 48 times smaller by the project's own arithmetic. Download size matters less than it sounds, since you only pull images once. The more useful number is idle RAM: the project reports about 140 MiB with 10,000 titles and 55,000 movies and episodes. That's a self-reported benchmark on one setup, so treat it as a direction, not a guarantee. Your library size, indexer count and hardware will move the number.
How a request moves through one app
Here's the flow HolyArrs follows, in order. Understanding it makes the rest of the setup easier to reason about.
- A user requests a title, or a whole season, from the Explore page.
- HolyArrs searches your Sources. These can be any Torznab or Newznab indexer, or a Prowlarr or Jackett instance.
- Your Pick rules choose the best release by size, quality and language.
- The release goes to your downloader, such as qBittorrent, Transmission, Deluge, SABnzbd or NZBGet.
- The finished file is filed into your library, and your media server (Plex, Jellyfin or Emby) is notified.
Each step used to be a separate app. Now the handoffs happen inside one process, so a failure at step 3 shows up in the same Downloads table where you'd see a step 4 error. That's the practical gain. The trade-off is that you lose the per-app configuration depth you may have built up over years, which leads to the next question.
Moving from Sonarr, Radarr and Prowlarr without breaking your library
Migration is the part that decides whether this is worth your weekend. In Settings > Move from other apps, you add each old app's address and API key or import a backup zip, choose what comes across, run Try it, then press Move. You can undo a move later.
What comes over:
- Library folders, titles and quality profiles, which become Pick rules
- Exclusions, naming and indexers from Sonarr, Radarr and Lidarr
- Indexers from Prowlarr, which become Sources
- Default subtitle languages from Bazarr
- People and their requests from Seerr or Overseerr
- Downloaders from qBittorrent and SABnzbd
What doesn't:
- API keys and passwords, which you retype or import from a file
- Custom formats, tags and history
- Media files, which never move
HolyArrs only reads your old apps and changes nothing in them. That means you can run both stacks side by side until the new one proves itself. Don't skip that step. Check a few weeks of grabs and imports before you shut anything down, because custom formats are the most common thing people discover they miss after the switch.
Where HolyArrs still falls short
Here's where most guides stop being honest. HolyArrs is young, and the README is candid about its gaps:
- It doesn't download by itself. It connects to qBittorrent, SABnzbd and the others. It doesn't replace them.
- No AI or MCP features in 1.0.
- No phone or TV apps. The web app works on a phone, but there's no native client.
- Finding subtitles online comes after 1.0. Subtitles you pick are kept with the file, but HolyArrs won't go looking for them yet.
That said, these gaps matter differently depending on your setup. If you rely on custom formats for fine-grained release scoring, the missing history and tags could be a deal-breaker. If you mostly want requests approved and files filed without thinking about them, the gaps are less likely to bite.
When to keep the six-app stack
This is the trade-off most readers actually need. Keep the separate *arr apps if you run a complex, tuned setup, use custom formats heavily, or rely on tags to route different content to different download clients. The per-app depth is real, and HolyArrs doesn't claim to match it yet.
Consider HolyArrs if you run a household server, you're the one person who fixes things when they break, and the number of logins and API keys is what wears you down. A smaller footprint and one place to look is a genuine advantage for that profile.
Frequently Asked Questions
What is a Sonarr Radarr alternative?
A Sonarr Radarr alternative is an app that covers what Sonarr (TV) and Radarr (movies) do, usually alongside other media types. HolyArrs is one example. It combines shows, movies, music, indexers and requests into one self-hosted app with one login and one web port, and it can import your existing Sonarr and Radarr settings.
how do I move from Sonarr and Radarr to HolyArrs?
Open Settings, choose Move from other apps, and add each old app's address and API key or a backup zip. Pick what to import, run Try it to preview, then press Move. Your old apps stay untouched, so you can run both side by side. Custom formats, tags and history don't transfer, and you'll need to retype keys.
why do Sonarr and Radarr need separate logins and API keys?
Each *arr app is an independent service with its own web interface and configuration. To make them cooperate, you copy API keys between them. A single app avoids this because the search, release picking and download steps share one configuration and one process.
Does HolyArrs download torrents or Usenet files itself?
No. HolyArrs sends releases to a separate downloader such as qBittorrent, Transmission, Deluge, SABnzbd or NZBGet. It handles searching, picking, requesting and filing the finished files into your library.
Is HolyArrs ready to replace my whole media stack?
It depends on what you use. HolyArrs is pre-1.0 in places, with AI, MCP, native phone and TV apps and online subtitle search deferred. Run it alongside your current stack for a few weeks before you turn anything off.
Try the migration preview this week and check whether the Pick rules match what your old quality profiles chose. If your household is wrestling with six logins and a missing show nobody can explain, pass this along to whoever maintains the server. Their first step is to run Try it on a single app's settings, and see whether a Sonarr Radarr alternative with one login fixes the tangle.