After the beta, all your reports, and a lot of late nights, Quartermaster is now live on the App Store. A lot of it has been mixing this with work and development :D (dev as a job)

https://apps.apple.com/gb/app/quartermaster-homelab-stack/id6779994284

Feel like I need to say this before anything because the App Store is drowning in it right now. Quartermaster is not vibe coded, and it is not a thin copy paste wrapper around one arr app's API like so much of what is flooding the store. It is a real, hand built native app in Swift and SwiftUI, designed screen by screen. And it is broad in a way I have not found anywhere else, not just your arr apps, but discovery and requests, your downloaders, your media servers, and the infrastructure underneath, from containers and VMs to DNS and smart home, all in one place. This is why the feedback was great in regards to QM feeling native, handles the awkward edge cases, and tells you the truth about your stack instead of guessing.

For anyone new here, Quartermaster is a native iOS app for controlling your self-hosted stack from your phone. Browse your library, request films and shows, watch what is downloading, and keep an eye on your servers, all in one fast app that actually feels like it belongs on iOS.

It is a pure client. It talks straight to the services you already run on your own hardware, your credentials are stored encrypted on your device, and there is no Quartermaster account, no relay server, and nothing sitting in the cloud in between. Your data stays yours.

What it connects to:

- Media: Radarr, Sonarr, Lidarr, Jellyseerr, MusicSeerr, Prowlarr, NZBHydra2, Bazarr, SABnzbd, NZBGet, qBittorrent, Transmission, Deluge, Jellyfin, Emby, Plex and Tautulli

- Infrastructure: Portainer, Glances, Unraid, Proxmox, AdGuard Home, Pi-hole, Cloudflare, Home Assistant, Immich, AudioBookshelf, Komga, Kavita and Tdarr

To everyone who tested (over 250!): thank you, genuinely. A huge amount of this app came straight from your reports, and it would not be what it is without you. I am keeping a smaller group of the most active testers on TestFlight for early builds as a thank you.

If you give it a go and it clicks for you, an App Store review would mean the world right now. It makes a real difference for a brand new app. And this sub is the place for support, feedback and feature requests, so post away.

Guys the support has been amazing - https://discord.gg/RaurxUTutx - I have just created this to help the ones having issues, questions or new features, please join :)

v1.12.14 is out. This is the first stable release after the 1.12.0 beta cycle and brings a significant amount of new features alongside some important bug fixes.

Download

Windows Installer / Jellyfin & Emby Plugins: https://github.com/JFLXCLOUD/NeXroll/releases/tag/v1.12.14

Docker: jbrns/nexroll:latest

What's New

Sequence Builder — 3 New Block Types

NeX-Up Trailers, Coming Soon List, and Dynamic Preroll are now available as sequence blocks. Full support across the block editor, timeline, statistics, preview, export/import, scheduler, and Plex apply.

Emby Server Support

Emby is now a first-class media server alongside Plex and Jellyfin. A dedicated NeXroll Intros Plugin handles Cinema Mode preroll injection.

Conflict Resolution Page

Replaced the popup wizard with a dedicated Conflicts tab. Side-by-side schedule comparison, Auto-Resolve All, and persistent ignored conflicts.

Monthly Schedule Overhaul

Monthly schedules now use a Jan–Dec month selector instead of date pickers, with an optional time window per day.

Other additions: yearly schedule type, dashboard countdown timer to next activation, forgot password / local reset, drag & drop upload, EN/FR/ES/DE language support for NeX-Up generators, Coming Soon List logo positioning options, max trailers expanded to 50 / No Limit, API keys bulk delete, random block rotation every 10 minutes.

Bug Fixes

Jellyfin plugin fails to load on Jellyfin 10.11.x — The plugin DLL was compiled against an older SDK, causing a ReflectionTypeLoadException on startup. Rebuilt against 10.11.x — grab the updated DLL from the release page.

Radarr / Sonarr HTTP 307 in Docker — Connections now follow redirects, fixing failures when a Base URL or reverse proxy is configured in your Docker setup.

Other fixes: event log per-row scrollbars, scheduler silent fail on null sequence, NeX-Up orphan records in random pools, sequence preview Now Playing desync, plugin detect API key leak, preview player skipping, Plex disconnect token deletion, update checker version comparison, Docker CVE remediation.

Full changelog: https://github.com/JFLXCLOUD/NeXroll/blob/main/NeXroll/CHANGELOG.md

As always, report issues on GitHub, Discord - Help-Desk or leave a comment here.

It's Friday, Digarr just passed 100 stars on GitHub, and v1.10.0 is out. That's the first stable 1.x line, so it felt like a good moment to share it properly.

Digarr is a self-hosted music discovery layer that sits in front of Lidarr (or your media server). It learns what you listen to, asks an AI provider for new artists and albums, scores them, and hands you a review queue. You approve what you like and it goes to Lidarr or a playlist target. The data stays on your server.

A few things I think it does well:

• An AI taste pipeline you actually control. It builds a profile from your listening sources, asks your AI provider for candidates, then scores them with weights you set (consensus, similarity, genre overlap, AI confidence, popularity, and learning from your past approvals). You pick the provider: Anthropic, OpenAI, Gemini, Ollama, or any OpenAI-compatible endpoint. Point it at Ollama on localhost and nothing leaves your box.
• Album-level discovery. Most tools only recommend artists. Digarr also finds individual albums: studio albums you are missing from artists you already follow, new releases you missed, and net-new finds from artists you don't have yet. Approving an album adds the artist to Lidarr unmonitored and grabs only that album, so you don't pull a whole discography to get one record. As far as I can tell, nothing else in this space does album-level discovery.
• Mood discovery. Type "something like Boards of Canada but darker" or "upbeat 90s pop for a road trip" and it turns that into a result set. No filter-building first.
• Works with or without Lidarr. If you don't run Lidarr, discovery-only mode still works and pulls from ListenBrainz, Last.fm, Spotify, Deezer, Plex, Jellyfin, Emby, and Discogs.

The basics, in short:

• Connects to Lidarr, Plex, Jellyfin, Emby, and slskd, plus ListenBrainz, Last.fm, Spotify, Deezer, and Discogs
• Review queue with approve / reject / skip, swipe on mobile, card stack on desktop
• Discovery modes (Artist Radio, Release Radar, Library Gap-Fill, Charts, Deezer Flow, Spotify Saved Albums, and more) you can run on demand or schedule as subscriptions
• Auto-playlists to Navidrome, Jellyfin, Emby, Plex, or Spotify, or export as M3U / XSPF
• Genre browser, decade filter, cross-platform search, 30-second previews
• Multi-user with OIDC/SSO and per-user sources, weights, and targets
• Backup and restore, job history, webhook notifications (Discord, Slack, ntfy, Gotify) with an optional scheduled digest
• 15 UI languages with locale-aware AI output, 15 color themes in dark and light
• One container that runs next to your existing stack. Free and open source, MIT.

On the AI question, since it always comes up: this is built with AI assistance, and I drive it. I set the roadmap, design the architecture and the UX, decide which features ship, and review every change. The AI writes most of the code and tests under that direction. I'd rather say that up front than have someone find it in the commit history.

GitHub: https://github.com/iuliandita/digarr

Happy to answer questions, and bug reports or feature ideas are welcome in the issues.

What is Scryer?

Scryer is a new open source application written from scratch that does what Sonarr & Radarr do in a single, tiny binary. However, Scryer is more than just a clone. I put together a comparison page that explains how i'm approaching this differently and why you may prefer it for more than just RAM reduction.

I'm humbled at the overwhelming support and feedback I've received since my launch post. This passion project has been so much fun for me to work on and I'm loving that others are finding it useful! I am so thankful those who have put time and effort into commenting, chatting with me, and posting GitHub issues.

Release 0.15.0

Full release notes here

You voices were heard and I reprioritized things for this release. Here's the headlining features:

• Prowlarr support
  • Instead of configuring Scryer in Prowlarr, you configure Prowlarr as an indexer in Scryer and it will sync all your Prowlarr managed indexers
  • Works great in my testing with the *nab services I have access to in
• Postgres support
  • Thanks to those who asked for this. While it was quite the lift, it was well worth the effort.
• Sabnzbd Proxy Support
  • I tested with NzbDav, it may work with other tools. If you run into issues with any of the others please let me know on GitHub!
  • I also added the ability to route libraries to specific clients like Sab/Nzbget. This makes it simple to have a mixed catalog of sources.
• Enhanced metadata and matching
  • I augmented the metadata sources to include a lot more data from TMDB as well as enhancing the search indexes to provide more intelligent matching on library scans

What's coming?

0.16.x will bring the foundations for Seerr functionality. I am passionate about cyber security and if folks are opening Scryer on their edge, it must be hardened. This will include enhanced login security options in Scryer, as well as account linking for Jellyfin. I also plan to have the first version of the request flow in 0.16.x.

Feel free to browse the code or create issues on GitHub:

https://github.com/scryer-media/scryer

Not sure if this has already been done but couldnt find it so made it myself. I dont use a phone to add stuff to sonarr/radarr with things like nzb360, however i do stream content from jellyfin via android tvs, my current flow is to go into my office, go into sonarr/radarr webui download then go back to the livingroom/bedroom and watch - so built these so i can just download from the tv itself.

used ai for some development.

https://github.com/WB2024/Sonarrdoid/releases/tag/v1.0

https://github.com/WB2024/Radarroid/releases/tag/v1.0

any thoughts and ideas welcome

Hi Guys,

If you run your own media server, you probably know the usual setup.

One app for Sonarr. Another for Radarr. A separate download client. Then Jellyfin or Plex for watching. Most of the time the mobile experience feels clunky, outdated, or just made for desktop browsers.

That’s exactly why I started building ARFlix. The goal was simple: bring everything together into one clean and modern experience that actually feels good to use on a phone.

Instead of jumping between different apps and web dashboards, ARFlix lets you:

• Browse and stream your media library
• Manage movies and TV shows
• Monitor downloads in real time
• Check upcoming releases and missing episodes
• Connect with your existing setup like Sonarr, Radarr, Jellyfin, and more
• Use a UI that feels closer to Netflix instead of old admin panels

I’ve been putting a lot of focus into performance, smooth animations, and making the app feel polished instead of looking like another wrapper around web pages.

Everything connects directly to your own server. No accounts, no subscriptions, no cloud lock-in.

The Play Store listing just went live, and pre-registration is now open. I’d genuinely love feedback from people in the self-hosted and homelab communities because this app is being built for users like us.

https://play.google.com/store/apps/details?id=com.bitkreativ.arflix

Hey all,

I’ve been running a pretty standard *arr setup for a while and kept running into the same annoying issue — backups/archiving.

Stuff like:

• External drives getting out of sync
• Not knowing what’s actually backed up vs not
• Copying a bunch of random junk files along with media
• No good way to track what lives on which drive

AND MOST IMPORTANTLY

• Being required to have all archive drives plugged in at once to track what is backed up.

After dealing with that way too many times, I ended up building a small app to handle it.

It’s called Archivarr: https://github.com/DanBrown95/archivarr

---

What it does (at a high level)

It’s basically a companion app for *arr stacks that focuses on:

• Backing up media in a smarter way (movies, shows, music + useful metadata)
• Skipping a lot of the random extra files you don’t actually care about
• Keeping track of what files exist on which archive drives (especially helpful for offline/cold storage)
• The ability to regularly schedule scans of your media directory

It doesn’t try to replace Sonarr/Radarr or anything — it just sits alongside your setup and allows you to track whats backed up where, what needs to be backed up, and a one click archive process.

---

Why I made it

Most of the tools I tried were either:

• too generic (rsync scripts, etc.)
• or just didn’t really “get” media libraries

What I actually wanted was something that could answer:

“Do I already have this backed up somewhere?”

without digging through drives manually and requiring all archive drives to be live.

---

Current state

It’s stable enough that I’ve created a v1.0.0 tag and am using it myself, but there are gaps and I would love community feedback and involvement to really make this a *arr companion app.

If anyone wants to try it out, I’d really appreciate:

• feedback (even “this is confusing” helps)
• bug reports
• feature ideas

---

Stuff I’m thinking about adding

• ability to set scheduled archive jobs (currently supports scheduled scan jobs)
• tighter integration with Sonarr/Radarr
• performance optimization
• mobile friendly/responsive UI

---

Anyway, figured I’d share in case this solves a problem for anyone else.

Happy to answer questions or hear how other people are handling archives.