Do you still need Plex, Jellyfin, and the arr stack?
By Jrm, who builds Cinaura · Updated August 2026 · 5 min read
There is a standard recipe for owning your own media, and most people follow it without ever asking why. Put Plex or Jellyfin on a machine that never sleeps. Add Sonarr and Radarr to go and fetch things. Prowlarr underneath to feed them indexers. Bazarr for subtitles. A download client below that. Overseerr on top so the household can request things. Tautulli to watch the watchers. Eight moving parts, a reverse proxy, and a compose file you are quietly afraid to touch.
That recipe was written around 2015 and it was right at the time. Nobody has updated it since, and several of the problems it solves have quietly stopped existing.
The stack does two jobs, and people always talk about them as one
Every container in that list is doing one of two things. Acquisition, which means getting content onto your storage. Presentation, which means turning a pile of files into something with posters, seasons, and subtitles that behaves properly on a television.
Hold those two apart for five minutes and the whole argument gets simpler, because one of them is now entirely solvable without a server, and the other one has moved somewhere else.
Transcoding fixes a problem you probably do not have
Transcoding is the load-bearing justification for the whole server. It exists to re-encode video on the fly for clients that cannot handle the original file, which in practice means a phone on hotel wifi or a browser tab.
Watch on your own television, on your own network, and none of that applies. A current Android TV box direct plays H.264, HEVC, and AV1, handles HDR10, HDR10+, and Dolby Vision, and passes TrueHD and Atmos straight through to the receiver. Nothing needs converting because nothing is wrong with the file. You are running a CPU-hungry service to fix a mismatch that does not exist in your living room.
Cinaura leans on that hardware rather than working around it. It matches the display refresh rate to the content frame rate, handles HDR end to end instead of tone mapping it, falls back cleanly on Dolby Vision Profile 7 files that other players render as a black screen, and passes audio through untouched. That is the entire job the transcoding server was doing for you, done by a box you already own.
Jellyfin fixed the price, not the server
Plex made this conversation urgent in 2026. Remote streaming moved behind the paid tier and the lifetime pass went from $249 to $749, which is a question of its own. Plenty of people responded by moving to Jellyfin, and it is a genuinely good project. Free, open source, no account, nobody raising the price on you.
But look at what actually changed. You still install a server. You still keep it patched. You still forward ports or stand up a reverse proxy to watch anything outside the house. You still get the call when it breaks on a Friday night. Jellyfin solved the billing problem and left the maintenance problem exactly where it was.
That is the trade almost nobody names out loud. Going from Plex to Jellyfin is changing landlords. It is not moving out.
The audit
Piece by piece, here is what each part of the stack was doing, and what covers it now.
| What you are running | What it does | How Cinaura handles it |
|---|---|---|
| Plex or Jellyfin server | Serves your library out to client apps | Cinaura connects straight to your sources and keeps the library on the device. Nothing to install, patch, or leave running |
| Transcoding | Re-encodes video for clients that cannot play the file | Cinaura leans on what a modern Android TV box already decodes, and adds frame-rate matching, HDR end to end, and audio passthrough |
| Reverse proxy, VPN, Tailscale | Exposes the server safely outside the house | Nothing is served, so there is nothing to expose or lock down |
| Bazarr | Hunts down and downloads subtitles | Cinaura searches OpenSubtitles in the app, picks up sidecar files on scan, and handles styling and timing offset |
| FileBot, tinyMediaManager | Renames and tags files so the server can match them | Cinaura parses filenames as it scans and reads your existing NFO files, so past curation carries straight over |
| Metadata agents | Fetch posters, cast, and episode data | Cinaura matches against TMDb for posters, seasons, cast, and collections, and lets you pin the right result when it guesses wrong |
| Overseerr, Jellyseerr | Lets the household request titles | Not needed. A request queue only makes sense when something automated is doing the fetching |
| Tautulli | Reports who watched what, and when | Not yet. Per-profile watch stats are coming, and the data behind them is already sitting on the device |
| Checkrr, Maintainerr | Scan the library for corrupt, missing, or dead files | Cinaura flags this as it goes. Every source carries a live health state, and anything that disappears stays in the library marked unavailable with the date it went, so you can see what broke instead of finding out at play time |
| Sonarr, Radarr, Prowlarr, download client | Watch for releases and pull them onto your storage | Handled outside the app, and more simply. Search and add in your debrid service or a front end like Debrid Media Manager, and Cinaura picks it up on the next scan |
| Watching on a phone or a laptop | Plays your library away from the television | Not yet. Cinaura is built for the television first, but a mobile app is coming, and cross-device sync with it |
The acquisition half moved, it did not vanish
Sonarr and Radarr are automation for a specific job: pulling files down onto storage you own and tidying them up afterwards. That job barely exists on a debrid service. The content is already cached, so you search and add inside the service and it appears. The debrid providers have their own search, their own feeds, and a healthy ecosystem of tools around them. What used to take four containers is now a browser tab.
If you run a purely local library with no debrid in the picture, that is the one case where the arr stack still earns its keep, and Cinaura will happily read the NAS it fills over SMB.
What is actually left
Two pieces. A place your content lives, which is a debrid account, cloud storage, or the NAS already in the cupboard. And an app on the television that reads all of them and presents them as one library, with posters, seasons, subtitles, and resume. No always-on machine, no compose file, no port forwarding, and no update that breaks playback the evening you have people over.
Where this goes next
Cinaura is built for the television first. That is the reason it can skip the server, and it is also the current boundary. Watching on a phone or a laptop is the thing people ask for most often. A mobile app is close, and cross-device sync follows it.
Some setups will want more than this. Households with complicated sharing, or people who enjoy running their own infrastructure. The aim was never to cover every configuration, only to make the common one simple.
Every piece of that stack answered a real problem once. Hardware and services have solved most of them since, quietly, while the recipe stayed the same. Worth knowing which parts you still need, and which parts you keep out of habit.
If that turns out to be fewer than you expected, Cinaura is free on Google Play. Point it at what you already own, and see how much of the stack you actually miss.