DEV Community

Cover image for Consolidate Media Management Apps - HolyArrs Alternative
GitHubOpenSource
GitHubOpenSource

Posted on

Consolidate Media Management Apps - HolyArrs Alternative

TL;DR: HolyArrs operates as a unified self-hosted backend that integrates downloading, indexing, subtitle management, and requests into a single Go-based application.
Best for: Self-hosters and homelab administrators managing personal media libraries.
Repository snapshot: ⭐ 1 264 stars · 🍴 65 forks · Go · AGPL-3.0
Daily picks: Follow GitHub Open Source on Telegram


What it is

HolyArrs is a unified, self-hosted Go application that consolidates the functionality of traditional media management stacks into a single binary. Written in Go and licensed under open source terms, it replaces multiple discrete containers for shows, movies, and music with one 16.1 MB executable.

How it works

The application operates by exposing a single port and web interface, eliminating scattered dashboard tabs. It communicates directly with download clients and media servers to manage the complete lifecycle of media files, handling indexing, downloading, subtitle management, and requests internally.

Key features

  • Extremely lightweight footprint: approximately 16.1 MB package size utilizing roughly 95 MiB of idle RAM.
  • Browse media via an interface featuring inline trailer playback on hover.
  • Import existing setups directly from Sonarr, Radarr, Lidarr, Prowlarr, and Bazarr.
  • Configure custom pick rules based on file size, quality, and preferred language.
  • Receive release alerts across Discord, Telegram, ntfy, Gotify, Pushover, or webhooks.

Getting started

To run HolyArrs, clone the repository from GitHub and compile the Go binary or deploy the provided container image. Point the application to your existing media directories, configure your download clients, and use the built-in migration tools to pull in rules from your previous setup.

When not to use it

Avoid this tool if you rely heavily on specialized plugins unique to mature separate applications, or if you are not prepared to migrate your existing configuration databases away from the traditional multi-container stack.


Discuss

Which of the six legacy media apps would you drop first?

Curated from the repository README and metadata. No hands-on test is claimed; evaluate it in a sandbox before production use.

Top comments (0)