u/ionstat

Hey,

I'm the developer of Conductarr — a native Android app that manages the whole *arr stack from one place. I've been lurking and running the same kind of setup as most of you for years; after watching LunaSea slide into maintenance mode I built the thing I wished existed. It's in closed beta on Google Play right now and I'd love some testers plus honest feature feedback.

What it connects to:

• Sonarr (TV)
• Radarr (movies)
• Prowlarr (indexer manager + manual search across every indexer at once)
• Lidarr (music)
• Readarr (books)
• Bazarr (subtitles)
• qBittorrent
• SABnzbd
• Overseerr / Jellyseerr

All in one app, multi-instance per service (run two Sonarrs, a 1080p Radarr and a 4K Radarr, two qBittorrents on different VPNs — Conductarr just keeps them straight via an instance switcher in every header).

What it actually does:

• Browse and add to your libraries with full metadata-source search
• Manual indexer search through Prowlarr, push the result straight to Sonarr or Radarr in one tap (killer feature for me)
• Approve / decline Overseerr / Jellyseerr requests
• Watch the SAB queue and qBittorrent torrents live, with per-row pause / resume / delete
• Push notifications via FCM (zero-config) or ntfy (zero-data-through-us — point it at your own server), both at once if you want, with per-event-type routing rules
• Encrypted config backup (AES-GCM + passphrase) so switching phones isn't a setup-from-scratch ritual

Privacy by design (the bit you care about):

• API keys live in Android Keystore on your device only — never on a server I control
• The app talks directly to your *arr instances. No proxy, no relay
• No account system, no analytics SDK, no ads
• The only third-party data flow is opt-in Sentry for crash reports, which only fires on actual crashes
• Reverse-proxy aware (set urlBase if your Sonarr is at /sonarr behind Caddy / nginx / Traefik)
• Self-signed cert toggle for instances on homelab-only TLS, and it works with Tailscale / Cloudflare Tunnel / WireGuard out of the box

How it compares to what's out there:

• LunaSea — comprehensive but in maintenance. Conductarr aims to pick up where it left off.
• nzb360 — Android-only, dated UX, pretty aggressive paywall.
• Helmarr — iOS only.

Free vs Pro:

Free covers Sonarr + Radarr + Prowlarr + qBit/SAB with one instance per service. Pro (£4.99 lifetime, one-time) adds Lidarr / Readarr / Bazarr / Overseerr / Jellyseerr screens, unlimited instances, manual indexer search, encrypted backup, home-screen widgets, a Wear OS companion (full watch app + tiles + complications), automation hooks (broadcast intents for Tasker / Macrodroid / Llama) and custom themes / launcher icons. No subscription, no telemetry tier, no "10-instance gate" once you've paid. The first 50 testers will get a free lifetime redemption key.

Join the closed beta:

Join the Google Group (no information is public to other members) https://groups.google.com/g/conductarrtesters/ and once you've joined this group, you will then get access to the closed beta to install. Link for the beta is here:

https://play.google.com/apps/testing/app.conductarr.conductarr

One-tap opt-in with your Google account; the app installs straight from Play and auto-updates as new versions ship.

Looking for:

• Multi-instance users — I want to break the instance switcher under load (Pro is unlimited; please push it)
• Anyone running Sonarr / Radarr behind Tailscale or a Cloudflare Tunnel — cert handling is the bit I'm least confident about
• People who use ntfy push — I want event-routing edge cases
• qBit users with category / tag setups
• Feature ideas. I have a roadmap but it's mine; I'd rather build what people actually want. If there's a thing nzb360 / LunaSea / the *arr web UIs do that you wish a mobile app did better — say so in the comments. Same goes for things none of them do that you've always wanted. Upvotes on suggestions are a real signal I'll use to decide what lands in v0.2.

Happy to take bug reports, feedback and pushback on anything — the app is in pre-launch shape, things will break, I'd rather solve the breaks now than after the public release.

Specifically for feature requests / pain points, dropping them as top-level comments here is the cleanest way — others can upvote and I can reply with "yes, that's planned" / "interesting, never thought of it" / "here's why that's harder than it looks." Or email hello@conductarr.app if you'd rather keep it off-Reddit.

The official dev account is u/Conductarr — I'll be replying from there in the thread for anything support-shaped, so future searchers can find a clear answer trail.

Cheers.

EDIT: changed instructions for sign up to the closed beta.