187
submitted 1 week ago* (last edited 1 week ago) by kiol@lemmy.world to c/selfhosted@lemmy.world

Seems this just released 10 hours. Was mentioned in this other thread, but figured it was worth granting it's own topic. Very Cool! I'm not the dev, but this is awesome. Was originally posted to Reddit here.

Oh wow, repo is https://github.com/LLukas22/Jellyswarrm

Jellyswarrm is a reverse proxy that lets you combine multiple Jellyfin servers into one place. If you’ve got libraries spread across different locations or just want everything together, Jellyswarrm makes it easy to access all your media from a single interface.

Working

  • Unified Library Access – Browse media from multiple Jellyfin servers in one place.
  • Direct Playback – Play content straight from the original server without extra overhead.
  • User Mapping – Link accounts across servers for a consistent user experience.
  • API Compatibility – Appears as a normal Jellyfin server, so existing apps and tools still work.

⚠️ In Progress

  • Websocket Support – Needed for real-time features like SyncPlay (not fully reliable yet).
  • Audio Streaming – May not function correctly (still untested in many cases).
  • Automatic Bitrate Adjustment – Stream quality based on network conditions isn’t supported yet.

🚫 Not Planned

  • Admin Functions – Server administration (user management, settings, etc.) won’t be supported through Jellyswarrm.----
top 26 comments
sorted by: hot top controversial new old
[-] Grandwolf319@sh.itjust.works 28 points 1 week ago* (last edited 1 week ago)

Holy shit, sounds like this would enable people to have a community in which m every person has a Jellyfin and they each use all of them.

One person could specialize in documentaries and another in shows.

Combined, it would mean a huuuge library.

I wonder how high demand content would work. As in, if a TV show is watched a lot, could it be saved in multiple servers and the swarrm figure out who streams from what to balance demand?

[-] kiol@lemmy.world 16 points 1 week ago

Keep in mind this isn't federation. It is a way to access multiple independent servers via reverse proxy.

[-] Revan343@lemmy.ca 5 points 1 week ago

Yes, but a group of friends could use it to set up a group Jellyfin, sharing their libraries

[-] xnx@slrpnk.net 1 points 1 week ago

How would each person contribute to it?

[-] Revan343@lemmy.ca 8 points 1 week ago

By ripping their legally bought DVDs, surely :P

[-] xnx@slrpnk.net 1 points 1 week ago

I mean how would they upload their files to the server

[-] KairuByte@lemmy.dbzer0.com 6 points 1 week ago

It’s their own server, so they’d just… upload it.

[-] kiol@lemmy.world 1 points 1 week ago* (last edited 1 week ago)

Jellyfin plays the media. It doesn't make/produce/edit or upload the media. Think of it as DIY Netflix service

[-] BlueEther@no.lastname.nz 1 points 1 week ago

um, they don't

Each run their own jellyfin server and I guess their own jellyswarrm to access al of their friend's servers? - Not read the docs though

[-] guynamedzero@lemmy.dbzer0.com 25 points 1 week ago

Dude I just saw a post where someone was asking if something like this existed

[-] kiol@lemmy.world 16 points 1 week ago

Yep, this was mentioned in that thread and it is so impressive it deserves a dedicated topic to promote itself. Seems it has only existed for a few hours!

[-] sudo@programming.dev 21 points 1 week ago* (last edited 1 week ago)

Automatic Mapping

If a user already exists on one or more connected servers, they can log in directly with their existing Jellyfin credentials. Jellyswarrm will automatically create a local user and set up the necessary server mappings.

If the same username and password exist on multiple servers, Jellyswarrm will link those accounts together automatically. This provides a smooth experience, giving the user unified access to all linked servers.

Really should audit the implementation of that feature. So when you first log in it automatically sends you're credentials to every connected server?

[-] princessnorah@lemmy.blahaj.zone 9 points 1 week ago

I would assume it's a hash but yes, it needs an audit.

[-] exu@feditown.com 1 points 1 week ago

I'd assume you need an admin account for every server and it uses that to create the users.

[-] curbstickle@lemmy.dbzer0.com 9 points 1 week ago

Thats wildly cool... I'm checking it out tomorrow!

[-] avidamoeba@lemmy.ca 7 points 1 week ago

I feel like this problem should be solved via some form of federation within Jellyfin, but if Jellyswarm works well enough.. I'm not gonna make a fuss.

[-] comrade_twisty@feddit.org 4 points 1 week ago

Nice, this might finally allow me to have an English, German and French Library without having conflicts all the time.

[-] illusionist@lemmy.zip 4 points 1 week ago

How does it handle duplicate entries? How does it define duplicates?

[-] BlueEther@no.lastname.nz 3 points 1 week ago
[-] Cyber@feddit.uk 1 points 1 week ago
[-] sudo@programming.dev 3 points 1 week ago

I always thought this would make more sense to implement client side in the media player. But its probably easier to implement this way.

[-] Cris_Color@lemmy.world 3 points 1 week ago

I don't use jellyfin but these seems cool as fuck...

[-] kiol@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

Here are some thoughts from Jellyfin-offtopic:

  • I wouldn't trust it especially with the new DB coming out. No way Jellyfin's own DB supports multiple servers. It would be up to the tool to keep track of everything. And I'm assuming only one person is supposed to run that thing on multiple servers.
  • How would this work when multiple people want to connect to others at the same time?
[-] thagoat@lemmy.dbzer0.com 2 points 1 week ago

Thanks! Giving this a go tonight

this post was submitted on 24 Aug 2025
187 points (99.5% liked)

Selfhosted

51087 readers
18 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS