561
this post was submitted on 28 Nov 2025
561 points (98.3% liked)
Selfhosted
60542 readers
1333 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. Tags [CBH] or [AIP] are required, see the link 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. )
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
This is a "slippery slope' argument and thus a fallacy.
Let users decide how they want to run their own stuff. Right now if you have Plex pass this isn't an issue. If it becomes an issue, then you're in the exact same position you'd be in today if you decided to move away from Plex now.
I moved away from Plex years ago, but I don't blame users for sticking with it, it still has a lot of advantages over jellyfin.
EDIT: Y'all are trippin' over yourselves to complain about what other people choose to deploy on their own hardware.
I disagree. Right now you got time to do the research, plan the move and test it out with a demo setup. You do not know if you got the time if Plex decides to screw their lifetime users.
Yes this is hypothetical.
The steaks are very high. I could lose access to my media library for 1-2 evenings (the time it would take me to switch to Jellyfin).
Plex are trying to start a beef
Locking horns with users
It's entirely hypothetical. Jellyfin could also close source tomorrow, hypothetically (It happened with Emby so there's precedent).
Jellyfin can't go closed source as it's a fork of Emby from before it was closed source, licensed under the GPL. They don't own that code so they can't change that license, thus the whole project is GPL. In addition, Jellyfin isn't being developed by just one company (it's all volunteers), so every new contribution is also GPL licensed, owned by each contributor. The only way Jellyfin could go closed source would be to cut out the Emby backend and for every single contributor ever to agree to change the license, or have their code cut out. In short it's not happening, and if somehow it did the project would just get forked regardless for everyone to switch to (the community did it once already!).
No, you have not understood anything. Assuming Jellyfin would go closed source, (ignoring the GPL license and so on) you would not notice anything. Your server and service would be unchanged by this.
Emby is the best example, the community will fork it and you server lives on. Even if not, then the server and software is still yours.