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.
-
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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
The comments aren't doing a great job of explaining this but Plex can run on virtually any reasonably modern hardware: old laptops, thin clients, an old desktop, scrap parts. If you can get linux running on it, you can run plex for local network usage with one or two users.
Where hardware starts to matter is if you need to expose it to lots of simultaneous users or you need to do lots of transcoding. I do know of some users with giant libraries where the libraries can be a little slow to browse but it can be helped with a cache SSD for the metadata.
At this point the iGPU on intel processors is the easiest way to do transcoding and can handle a lot of streams with hardware transcoding. I used to have a nvidia card in my box and realized the iGPU was actually better anyway. I also think your streams should be direct play as much as possible. It's much easier and more efficient to have your library on a flexible format to start and just avoid on demand trsnscode.
If you need external access and need a VPN, you need a little extra power - or a separate device.
Now, OP didn't ask but I'll give my two cents on Plex vs Jellyfin.
Objectively, Plex is still the easiest to set and forget and is the most feature rich. I used it for something close to 15 years. I finally dropped it when I couldn't watch live tv anymore because of a known bug they just refused to fix for over a year. That was the last straw for me on top of all the enshittification.
I tried Jellyfin and found it lacking features and it was more difficult to manage securely. That led me to Emby. I'm not sure why it never comes up in these discussions. It's a nice middle ground. Jellyfin is a fork of Emby from when Emby decided to go closed source to try to figure out a sustainable financial model so they're very similar but Emby gives you back some of the convenience features from Plex.
But ultimately I think this is a personal preference and none of these are one size fits all. Plex is a reasonable place to start but, in my opinion, Emby is worth a look. Jellyfin is the ultimate choice for open-source, personal control, and privacy that the other two can't match because of their financial models.
As someone who's used all three (moved from Plex -> Emby -> Jellyfin):
Plex's killer feature is the relay and the fact it's completely transparent for users. You log in with a Plex client (whatever device, whatever location in the world) and it will sort out a connection to the Plex server. Complete no-brainer.
Jellyfin has been killing it lately, the last 3 versions (10, 11, 12) were all amazing leaps forward. The devs have been really hitting their stride and are addressing fundamental design issues and making Jellyfin better from the ground up. If you want complete independence, openness and control, excellent performance, this is it.
Emby for me sits somewhere in-between and it's not necessarily the better off for it. Feels like a compromise or the worst of both worlds. It has touches of Plex's enshittification streak, it hasn't addressed any of the core problems like Jellyfin has.
Both Emby and Plex have issues navigating VPNs and complex/unusual network setups because their plug'n'play approach relies too heavily on autodetection. Plex has the relay to fall back on (provided you pay for it) but Emby doesn't.
Both Emby and Plex will move features around and really, really want you to keep paying so it's anybody's guess what you'll be paying for from month to month. Lifetime passes were (can I say it?) a tremendously STUPID idea and now that ship has sailed anyway.
IMHO, one of these days someone will come up with a way for Jellyfin to provide free, transparent, aecure client+server pairing behind NAT and that will be a huge blow to both Plex and Emby.
I cannot vouch for this because I literally just found it two posts down after reading this one, but the developer of the JellyBox music player has a relay plugin for Jellyfin. It seems to specifically exist for the music player, but that's still useful for some people: https://github.com/JellyBoxPlayer/jellyfin-relay