this post was submitted on 10 Apr 2026
103 points (97.2% liked)
Selfhosted
60426 readers
585 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
as always, the answer is "it depends" - everyone has their own unique flavor of *arr stack with different components. Breaking it down, everything revolves around the core apps:
These apps do the majority of the hard work of going from eg. "I want this movie" to "this movie file is now downloaded and placed into a subdirectory on my NAS or storage somewhere"
Realistically, all you need to get started is a download client (usenet, torrent client, whatever - the most popular choice is qbittorrent-nox or an equivalent docker container), your *arr app(s) of choice, and a way to consume and share the media you've now downloaded to your NAS or server (plex, jellyfin, stash, audiobookshelf, VLC, etc)
For consuming media, here's a non-comprehensive list that most people will recommend at least one thing from:
The rest of the *arr ecosystem serves as a way to automate this core idea or fix issues with that automation. An example from my own homelab:
Not all of these will be useful to you, and you'll likely find others that are more useful for your situation. Like I mentioned, everyone's *arr stack is different and unique.
My recommendation: start with an *arr or two, configarr (optional but really recommended - hard to set up but once you do you're good forever), prowlarr (optional but you'll thank yourself later if you ever get into this and end up with more *arrs), and unpackerr (really do recommend this one) and go from there.
For anyone interested in the configarr config I use, here you go. It's somewhat customized to my taste (especially dubs > subs for anime) and there's likely an issue or inconsistency or two in it that someone more familiar might be able to spot, but it works pretty well and I'd say it's a good starting point if you just want to get going.
Note that it's a kubernetes ConfigMap but it's not hard to pull the relevant info into docker for your own needs.