For hardware acceleration you might be interested in the remote hardware acceleration strategy... https://jellyfin.org/docs/general/post-install/transcoding/ha

For hardware acceleration you might be interested in the remote hardware acceleration strategy... https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/#remote-hardware-acceleration https://jellyfin.org/docs/general/post-install/transcoding/h... The jellyfin DB itself is unfortunately sqlite instead of being DB agnostic. Maybe you could hack together something such that only one node handles writes and everyone else handles reads... if getting multiple cheap nodes gets your more bandwidth. I have to imagine that jellyfin fairly quickly stops being in charge of the media stream directly. But yeah I think the transcoding and the size of your data pipe is the only "hard" part. The DB read/writes themselves are going to not be an issue (I think)