Go
The serverOne Go process, with a smaller memory footprint as the goal.
In development · Coming soon
Movies, shows, music, subtitles and requests. Together in one app you run on your own server.
Click around HolyArrs the way it looks today, page by page, in dark and light. Or sit back and watch the tour.
Hover it. Watch it. Ask for it.
HolyArrs brings your library, subtitles and requests into one place.
Add your Sources and Downloaders once, then choose where they’re used.
Run it on your own server, alongside your download clients and media server.
I started HolyArrs in my own homelab, after looking closely at the apps around my media library.
36 apps covering library management, downloads, playback and the tools in between.
02 What it does
Add titles or scan files you already have.
Match releases to your quality, language and size preferences.
Handle stalled downloads and try another release.
Import finished files into their library folders.
Built to leave room for Jellyfin, game servers and your next container.

At idle. Leave more RAM for everything else.
Less time opening your library.
What we’re aiming for. Speed compared with Sonarr and Radarr; benchmarks come at release.
One Go process, with a smaller memory footprint as the goal.
One shared library database to back up.
A clean Svelte interface for the collection you built.
Docker on Intel, AMD and ARM64.
.NET servers.
HolyArrs: one Go process.
Python and Node.js.
HolyArrs: the same Go process.
React in the apps we studied.
Svelte in HolyArrs.
Separate SQLite databases by default.
One shared SQLite library database.
18 of 19 sections are done. Now the final boss: polish, audits, tests and a pentest before release.
Last updated
I’m Luis, also known as CoderLuii. I’m building HolyArrs for my own homelab, and I hope it makes looking after yours a little easier too.
I’ll send you a note when there’s something new to share, or HolyArrs is ready for your homelab.
Want to test it early? Join the beta testers on r/HolyArrs.