I agree that the rest of plex is undergoing enshittification. But the core features are kinda the same? I use it outside my home a LOT, so I don’t know how jellyfin would work for that. I know Cloudflare tunnel has a bad relationship with streaming video. Does Tailscale too? How do you access jelly outside your home?
I use Tailscale and it is absolutely fine. The problem is with other non tech savy people - the setup process is not straightforward so you need to help them a bit. They can’t just “connect”. But after that, Tailscale is great.
Controversial opinion and I say that as someone who started with Jellyfin and keeps that local Wifi only, so I admit a certain bias: going with Tailscale and Jellyfin over using Plex isn’t much better. Instead of enabling remote access via one company that wants to make money, you go via another company that wants to make money. How long is the free tier of Tailscale going to work out? How much do you trust them with your traffic? But I know it is a popular setup, so I am aware saying that here will not earn me any points.
Agree. I went directly with Jellyfin because I joined late the party, but never regret it.
So can’t comment on Plex, because I never used it. But I see the news and see the enshittified path it’s going on with Plex
I understand that they need revenue, specially if they actually provide the bandwidth to let you access your media from outside home. I also understand why people is mad, but I guess convenience come with a price, of you don’t want to pay for it, there are alternatives I don’t see anything bad in switching to jellyfin.
They don’t provide much in terms of bandwidth for you to access your own media. Just a few bytes through their web services. Their bandwidth usage comes from their desire to be their own streaming service. They provide access to a whole bunch of other media you may have no interest in.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System Git Popular version control system, primarily for code NAS Network-Attached Storage NVMe Non-Volatile Memory Express interface for mass storage Plex Brand of media server package RAID Redundant Array of Independent Disks for mass storage SSD Solid State Drive mass storage VPN Virtual Private Network VPS Virtual Private Server (opposed to shared hosting) nginx Popular HTTP server
[Thread #5 for this comm, first seen 8th Jun 2026, 12:50] [FAQ] [Full list] [Contact] [Source code]
Despite all of this, I haven’t completely abandoned Plex.
Plexamp remains one of the best self-hosted music applications I’ve ever used.
Lyrion, Music Assistant, and Navidrome are all solid options. And Jellyfin also supports music hosting, along with FinAmp, which has similar functionality to PlexAmp (maybe not as good, but download functionality works).
Personally, I abandoned PlexAmp. Wasn’t worth keeping with the rest and it has been downhill since the loss of Tidal integration. Navidrome clients work great, have solid radio and discovery features for large collections, and support local downloading for on the go.
And for local listening, I’d argue that Lyrion with Blissmix or LastFM “Don’t Stop the Music” plugins are as good and sometimes better than PlexAmp. And Navidrome and/or Music Assistant with AudioMuse-AI plugin utterly destroys PlexAmp’s radio/DJ functionality. Install AudioMuse, scan your library and go, it just works. Especially with recent builds having native Linux, Mac, and Windows now (I deployed with Docker compose before these options were available).
I’ve been considering audiomuse, but I have old equipment available.
My options are my media server, which is an old Xeon E3-1275v3 with 32G of RAM, which also hosts Navidrome, my arr stack and the associated downloaders, or my Home Assistant and Jellyfin box, which is a Lenovo M700 Tiny which is an i5 6600T but has only 8G of ram.
Or, an 8G Pi5 with an SSD (using the pi SSD hat)
I’m not sure either of those 3 options would handle audiomuse AI all that well…
The Xeon server would be a good bet. Your other machine would be potentially bottleneck for memory (though it meets min spec if the server isn’t doing anything else). There’s a NOAVX docker deployment available, would be slower but should work fine. Just be sure to disable anything associated with lyric detection, it’s an absolute performance nightmare.
I ran it on a Ryzen 5500u mini-PC with 32 GB RAM with the standard deployment with AVX2 support and scaled up to three worker threads. For a collection of 53k tracks it was processing about 100 per hour that way with lyrics/whisper translation enabled, but once I turned that off it was doing 1300-1400 tracks per hour.
——
Edit - the 6600T would work too. I found with lyrics disabled, each worker only used between 500MB and 2 GB of RAM. Long as the server isn’t under load while scanning I think that would work, and would be faster for having AVX2 support.
So.
I did a thing.
I have audiomuse-ai running its main, complete docker compose script, with all containers, on my 8GB Raspi5, and worker-only containers running on:
- An 8GB bhyve VM on my FreeBSD box
- An E2-6110 AMD pre-ryzen APU with 16GB of ddr3
- A Ryzen 5800x w 32GB RAM
They’ve been running about a week, and I’m a little over a third of the way through
Once the initial analysis is complete, I’ll stop all worker containers and leave it all just running fully on the pi5.
I also created a worker-only addon for the 6600T machine, but as it is already running HAOS and Jellyfin, I was getting a lot of OOM-related failures when it was running.
But I also have 32G of used, eBay bought, ddr4 SODIMMs.coming for it.
Bonus: Most of my homelab is in this. The only things missing are my Sophos running OPNsense, and the raspi5. Oh, and my actual desktop machine.
Yo, that’s awesome!
Pro tip for you, ASR (whisper - lyric detection/transcription) can be kind of bad, but if you have some spare resources, it takes very little to host a local LRCLIB database and clone lrclib.net (they have a GitHub page). This massively speed up lyric analysis for me using the API against a local site instead of getting 429s against lrclib.net or relying on ASR.
Lyrics are the biggest longest part of the scans. My whole collection was like 3+ weeks with lyrics stuff on, but only 2 days with just MusiCNN and CLAP.
