// the find
LLukas22/Jellyswarrm
Bring all your Jellyfin servers together
Jellyswarrm is a reverse proxy that presents several Jellyfin servers to a client as one, with merged libraries, user accounts mapped across servers, and merged Next Up and Recently Added lists. It is aimed at people whose media sits on their own machines and on friends' servers, and the README says plainly that it is still in early development.
- The security-sensitive state has been reworked deliberately. The migration history includes mapping encryption, session token encryption, and Argon2 hashing for local credentials, which is the part that would hurt users most if it were sloppy.
- The test setup exercises real servers. The dev environment runs six preconfigured Jellyfin instances plus Seerr, there is an integration compose file, and browser tests run in containers, so the proxy is not only checked against fixtures.
- The workspace is split sensibly. The Jellyfin client lives in its own jellyfin-api crate, the macros are separate, and build.rs compiles the web UI into the binary, so deployment is one container with no separate frontend to run.
- The README is honest about gaps. The in-progress list names QuickConnect, websocket reliability, missing adaptive bitrate, and missing media management, which makes it easier to judge fit before installing.
- Websocket support is not fully reliable yet, and SyncPlay depends on it. Audio streaming, progressive and HLS, runs through the video path. Anyone whose main use is synced listening or watching should expect rough edges.
- The README does not say what happens when a client cannot reach a remote server directly, for example behind NAT, a VPN, or a friend's firewall. Connecting servers across networks is the core pitch, so this is the scenario that matters most and it is left unanswered.
- The deployment example ships with a default login of admin / jellyswarrm. The warning comment is there, but copy-pasted compose files will run with it. The management UI at /ui also shares the client-facing port.
- Client compatibility is untested for most apps, by the authors' own FAQ. The 'works with your existing apps' claim therefore depends on which clients you use, and QuickConnect is still missing.