HolyArrs self-hosted on Proxmox: what it replaces and how to try it

HolyArrs is a new self-hosted app that does the work of Sonarr, Radarr, Lidarr, Prowlarr, Bazarr and Seerr in one container, with one login and one port. It does not play anything; Plex, Jellyfin or Emby still handle playback. On Proxmox you run it with Docker Compose inside an LXC container or a VM, and it is worth testing next to your current stack before you switch.

Media you download through it is your own responsibility, the same as with the rest of the *arr stack.

What HolyArrs replaces

The developer, CoderLuii on GitHub, explains the motive in the HolyArrs README: a normal media setup runs six apps, which means six logins, six ports, six update cycles and six API keys to copy between them. HolyArrs puts requesting, searching, release picking and library filing in one Go program, licensed AGPL-3.0. The repository went public on 9 November 2026 and had about 550 stars a day later.

The Show HN post called it "a 15 MB self-hosted Netflix and Spotify for your media server". In the Hacker News thread the developer said that label describes how browsing feels. Playback stays with your media server; read our Plex vs Jellyfin on Proxmox comparison if you still need to pick one.

What it connects to, per the README:

• Downloaders: qBittorrent, Transmission, Deluge, SABnzbd and NZBGet. HolyArrs does not download anything itself.
• Media servers: Plex, Jellyfin and Emby, which it notifies when a file lands.
• Sources: any Torznab or Newznab indexer, or an existing Prowlarr or Jackett.

Titles, artwork and charts come from a HolyArrs metadata server, so you do not need your own API keys for them.

How small it is

The README measured the six linuxserver.io images it replaces at 718.2 MB together on amd64 on 8 November 2026, against 14.9 MB for HolyArrs. It reports about 140 MB of idle RAM with 10,000 titles and 55,000 movies and episodes in the library. Images are published for amd64, arm64 and armv7.

Running HolyArrs on Proxmox

Proxmox gives you two places to run a Docker container: an LXC container with Docker installed, or a full VM. The trade offs are the same as for any media service, covered in our guide on whether to run Plex in LXC or a VM on Proxmox.

The README's quick start is a Compose file:

name: HolyArrs
services:
  holyarrs:
    image: holyarrs/holyarrs:latest
    container_name: holyarrs
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
    volumes:
      - /your/local/path:/config
      - /path/to/movies:/movies #optional
      - /path/to/tv:/tv #optional
      - /path/to/music:/music #optional
      - /path/to/downloads:/downloads #optional
    ports:
      - 6262:6262
    restart: unless-stopped

Then docker compose up -d and open port 6262. Create the owner account straight away: there is no default password, and whoever opens HolyArrs first becomes the owner.

Four details from the README matter on Proxmox:

1. Set PUID and PGID to a user with write access to your media and download folders. HolyArrs creates folders and moves files but never changes their owner.
2. Keep /config on local disk. The README says never to put it on a network share, so do not point it at an NFS or SMB mount from your NAS.
3. For moves that are instant and take no extra space, mount one parent folder that holds both downloads and library folders, and give your downloader the same mount at the same path. Separate mounts mean every import is a copy.
4. Do not forward port 6262 on your router. The README recommends a VPN such as Tailscale, or a reverse proxy with HTTPS.

Moving an existing *arr setup

Settings > Move from other apps takes each old app's address and API key, or a backup zip. You pick what comes over, run Try it, then Move, and you can undo the move later. The README says HolyArrs reads the old apps once and never changes them.

Keys and passwords stay behind, so you type them in again. Custom formats, tags and history do not come over, and media files never move.

Caveats for a project this new

It is a few days old. On Hacker News, commenters pointed out that releases ran from 1.0.0 to 1.0.10 within the first day. The developer replied that the code was private for months before going public and asked people to "treat this first week like a beta". Others questioned the size of the initial commit. Neither side is something you can settle from the outside, so treat it like any new service on your network: test it first, keep your old stack running, and update often.

Two operational points stand out:

• Back up the master key. holyarrs.key in the config folder unlocks the stored passwords and keys, and HolyArrs backups do not include it. As the owner, use Settings > Backups > Download key kit and store the copy somewhere else, along with your Proxmox backups of the container.
• The metadata server is a dependency. Several Hacker News commenters were uneasy that every install talks to a server the developer runs; the developer said bringing your own keys or provider is on the roadmap in issue 113.

The image has no shell inside it, so troubleshooting goes through the binary: docker exec holyarrs /holyarrs doctor checks the setup, and docker exec -i holyarrs /holyarrs reset-owner recovers the owner account.

For a homelab already running the six apps, the low cost way to judge HolyArrs is an LXC container with a copy of your config, using Try it before Move, while Sonarr and Radarr keep doing their jobs.