Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
Yes and no. You need to understand that no home service truly replaces Netflix, for a few reasons (the media might not be available on any of the services you're using, for example).
It's also not as simple as searching for a media in Jellyfin/Plex (or whatever other media frontend you choose, like Emby). There's a fixed flow.
But let's start by explaining the layers:
The frontend - Plex/Jellyfin/Emby/Kodi. This is what your users see, aka the "Netflix experience" - open the app, and all the media available on your storage device will be shown. Then they can click one and play it.
The request manager - Seerr (previously Overseerr/Jellyseerr). This is a separate interface where your users can request media. You still need to manually accept it (unless you set it up to automate things fully, but make sure you trust your users!). If something isn't available, your users will come here and ask for it, then the manager will show the status (requested, accepted, downloading, available). Once available, your users can watch it through the frontend.
The media managers - Radarr/Sonarr/Lidarr/etc. This is the software responsible for keeping a list of media you want, regularly looking them up on torrent trackers, Usenet servers, etc., and matching your requirements (resolution, language, encoding, file size, and so on), then grabbing the release and passing it on to the download client.
When you accept a request in the request manager, it passes on the info to the media manager, which adds the requested media to its internal list and begins looking for it.
At this point, control is passed back onto the media manager, which finds the freshly downloaded file, copies/moves it to the right place according to settings, renames it according to settings, marks it done then sends a signal to the request manager to indicate the request was fulfilled.
Finally, the media frontend, which is set up to watch the folder where the new media items are copied/moved and renamed, gets a notification that a new file is available, scans it, prepares metadata (poster, background image/music, description, actor and production lists, ratings, etc.), and makes it available in the search interface.
So the key differences with Netflix are:
That about covers all the functional differences between an arr stack and Netflix.