this post was submitted on 11 May 2026
702 points (96.8% liked)
Selfhosted
60409 readers
204 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
Jellyfin is FOSS. Taking a single step towards the Plex route will be going against the ethos of Jellyfin as a whole. It is community owned - rather than private, and if there are unethical practice's involved, then people can and will jump ship forking the whole project at nearly 1:1 scale.
Because of the way jellyfin is built and the underlying philosophy. It can't enshitify that easily as Plex - it will need a massive community effort to change it.
It is also useful to read on the history of jellyfin as it does highlight some useful pointers.
Also, Plex controls the login/authentication through their portal, and can also receive data back from your host regarding the content being shared/watched.
Jellyfin is 100% locally configured accounts
Jellyfin itself is Emby. Emby was owned by a company and it enshittified at the speed of light, and that's when Jellyfin was born (by forking the last open source version of Emby).
That's all correct, but.. we aren't absolutely in the clear. JF could absolutely be forked, DB changes enacted, security added, but you also need all those client devs to come along.
It's not quite like most Foss where a couple people could jump in and do a better job, JF has a LOT of moving parts supported by a number of individuals.