nzb360 and LunaSea are mobile API synchronization hubs, not Usenet downloaders. They connect to your self-hosted services, such as SABnzbd, Sonarr, and Radarr, over your local network or a secure remote connection, letting you manage your archival data stack entirely from your phone.
Running a home lab Usenet workflow from a desktop is straightforward. Running it remotely, especially when a queue stalls at 2 a.m. or a new public domain archive drops and you want to grab it immediately, is where a dedicated mobile controller earns its place.
The choice between nzb360 and LunaSea comes down to three things: your platform, your budget, and how much of your self-hosted media stack you need accessible from one interface. Both apps are recognized by the Servarr community as legitimate remote controllers. Both surface the same core services. The differences matter more as your homelab grows.
This guide walks through every meaningful distinction between the two apps, from platform support and pricing to security posture and daily usability, so you can configure the right one with confidence.
What These Apps Actually Do In A Usenet Workflow
Neither app retrieves Usenet articles directly. What they do is sit above your download clients and archival data organizers, pulling live data through their APIs and presenting it inside a clean mobile interface. The distinction between a controller and a downloader is worth stating clearly before comparing features.
Why A Mobile Controller Is Different From A Usenet Downloader
A Usenet downloader, such as SABnzbd or NZBGet, handles the actual work: connecting to your provider, fetching articles, assembling binaries, and verifying files. A mobile controller like nzb360 or LunaSea never touches that process directly.
What a controller does is send instructions and receive status updates. You tell it to add a title to Radarr. Radarr finds the NZB through your indexer. SABnzbd downloads it. The controller just shows you the result.
This separation matters for troubleshooting. If a download fails, the issue lives inside SABnzbd or your indexer configuration, not inside the mobile app.
How API Synchronization Hubs Fit Into A Self-Hosted Media Stack
Every service in a modern self-hosted media stack exposes an API. SABnzbd has one. Sonarr has one. NZBHydra2 has one. An API synchronization hub like nzb360 or LunaSea authenticates against each of those APIs using a unique key and aggregates the data into a single interface.
The practical result is that you stop opening four browser tabs on a small screen. One app replaces all of them.
Where NZB Files, Download Clients, And Indexers Connect
The flow runs like this: your indexer or meta search layer finds a matching NZB file, passes it to your download client, and your archival data organizer monitors the result. Your mobile controller observes and directs each layer without replacing any of it.
Indexers such as NZBgeek or NZBFinder surface the content. NZBHydra2 aggregates across multiple indexers. SABnzbd or NZBGet processes the NZB. Sonarr or Radarr manages the library. nzb360 or LunaSea ties the whole view together in your pocket.
NZB360 Vs LunaSea At A Glance
The sharpest split between these two apps is platform availability. One is Android-only and actively developed. The other is cross-platform, built on Flutter, open source, and currently archived. A successor is in progress and will remain FOSS, though it is expected to charge for app store distribution.
Platform Support And Current Project Status
nzb360 is Android-exclusive and available through the Google Play Store. Development is active, with recent versions adding support for services like Tautulli, signaling continued momentum. For Android users, it is the more mature option with the longer feature history.
LunaSea launched as a cross-platform Flutter app specifically because nzb360 was not available on iOS. The developer has been transparent: as of 2024, LunaSea entered an archived state. The existing build functions and has no critical bugs, but it is no longer receiving updates.
iOS users currently have LunaSea and the emerging Ruddarr as their main options. Ruddarr is free and open source but covers a narrower set of services than either of the primary contenders.
Pricing Model, Premium Value, And Long-Term Viability
LunaSea is entirely free in its current archived form. No paywalled features, no subscription, no in-app purchases.
nzb360 offers a limited free tier. The premium unlock is a one-time lifetime purchase priced around $7.49, which removes all restrictions. For anyone running a daily Usenet archival workflow, that cost is negligible against the time saved.
Long-term viability favors nzb360 for Android users. LunaSea’s archived status introduces uncertainty, particularly if the successor app shifts to a paid model at launch.
Open Source Vs Proprietary Tradeoffs
LunaSea is fully open source. The codebase is auditable, which matters to FOSS-oriented home lab builders who want to verify what the app does with their API keys and server addresses.
nzb360 is proprietary. You are trusting the developer’s implementation without the ability to inspect it. That is a reasonable trade for most users given the app’s track record, but it is a real distinction worth acknowledging for security-conscious setups.
| Feature | nzb360 | LunaSea |
|---|---|---|
| Platform | Android only | Android and iOS |
| Open source | No | Yes (FOSS) |
| Free tier | Limited | Fully free |
| Active development | Yes | Archived |
| Premium cost | ~$7.49 one-time | None currently |
| Successor project | N/A | In progress (FOSS) |
Supported Services And Stack Compatibility
Stack depth is where nzb360 pulls ahead for power users, while LunaSea holds its own across the core *arr services. The differences become more apparent once you move beyond Sonarr, Radarr, and SABnzbd into the broader Servarr ecosystem.
Core Arr Services For Archival Data Automation
Both apps support the primary *arr services: Sonarr, Radarr, and Lidarr. nzb360 also integrates Readarr, Mylar3, and Whisparr, giving it broader coverage across the Servarr ecosystem for users managing diverse archival data collections.
LunaSea covers Sonarr, Radarr, and Lidarr solidly. Its module-based architecture keeps each service in its own tab, which is clean but means switching context more often than nzb360’s blended dashboard approach.
nzb360 supports multiple simultaneous instances of each service, useful if you run separate Radarr instances for different archival categories. LunaSea handles this through its profile switching system, which works well once you understand the setup.
Indexer Layers And Meta Search Tools
Both apps connect to NZBHydra2 as a meta search aggregator sitting in front of your Newznab indexers. nzb360’s indexer search interface is more polished and has historically been the stronger implementation.
LunaSea added indexer support in version 2.0.0, bringing it closer to parity. Prowlarr, which has largely replaced Jackett as the preferred indexer manager in modern stacks, is supported in nzb360. LunaSea’s archived status means Prowlarr integration may not be fully current.
nzb360 also retains compatibility with legacy configurations, which matters for long-running home labs that have not migrated every component.
Requests, Monitoring, And Library Visibility Tools
nzb360 includes direct integration with Tautulli for library monitoring and activity tracking.
LunaSea’s Tautulli support exists but is less developed given the archived state.
Remote Access, Privacy, And Safer Setup
Connecting a mobile controller remotely means exposing your home lab’s API endpoints beyond your local network. How you handle that exposure matters significantly for the security of your self-hosted setup. Both apps support the same connection methods; the security posture depends entirely on how you configure your infrastructure.
Local Network Access Vs Secure Remote Endpoints
On your local network, both apps work immediately once you enter each service’s IP address, port, and API key. No special configuration is needed. This is the safest setup because your traffic never leaves your home network.
Remote access requires more care. Exposing SABnzbd, Sonarr, or Radarr directly to the internet without additional protection is a poor choice regardless of which mobile app you use.
Using SSL, HTTPS, And VPN Layers Sensibly
A reverse proxy with HTTPS is the standard approach for exposing home lab services remotely. You get SSL termination, a clean domain, and the ability to enforce authentication before traffic reaches your services.
A VPN layer, particularly a self-hosted solution, is an even cleaner option. You connect your phone to the VPN, and your home network appears local. Both nzb360 and LunaSea work transparently over this setup. The LunaSea community specifically recommends this approach in its documentation threads.
Docker and Docker Compose make deploying a reverse proxy straightforward alongside your existing containerized services.
Why API Exposure Needs Extra Care In A Home Lab
Every service in your stack uses an API key for authentication. These keys grant full control: queue management, library edits, configuration changes. If an API key leaks, an attacker has complete access to that service.
Best practices include rotating API keys periodically, never exposing services without authentication in front of them, and avoiding plain HTTP for any remote connection. nzb360 and LunaSea both store your API keys locally on the device; neither transmits them to external servers.
Daily Usability On Mobile
The real test of any mobile controller is how it feels at 7 a.m. when you want a quick queue check before work. Both apps handle the core tasks, but they approach the experience differently in ways that add up over time.
Queue Management, Search, And Notifications
nzb360 presents SABnzbd queue management, Sonarr and Radarr library status, and indexer search within a blended dashboard that feels native to Android. Clearing a stuck download, triggering a manual search, or reviewing recent history all require minimal taps.
Push notifications work in both apps. nzb360’s notification reliability is generally considered stronger across community feedback, particularly for download completion and failure alerts.
LunaSea’s module-per-service layout keeps things clean but means more navigation steps for users who jump between SABnzbd and Sonarr frequently.
Handling Multiple Servers And Dashboard-Like Workflows
LunaSea’s profile system is its strongest organizational feature. You can group all services for a given server into a named profile, then switch between profiles for different home lab environments. This works well if you manage more than one server instance.
nzb360 handles multiple instances differently, letting you configure several of the same service type side by side. It lacks the formal profile abstraction but achieves similar results.
Neither app attempts to replace full dashboard tools like Dashy, Homarr, Heimdall, Homer, Homepage, Organizr, or Flame. Those tools serve a different purpose as browser-based landing pages for your entire self-hosted stack, not native mobile controllers.
Which App Feels Better For Quick Check-Ins
nzb360 loads service data faster in most real-world conditions, especially on slower connections. The native Android implementation avoids the occasional animation lag that LunaSea’s Flutter framework can introduce on lower-end devices.
For iOS users, LunaSea is the only full-featured option available right now, and it performs well on Apple hardware. The comparison only becomes meaningful for Android users choosing between both.
Which App Fits Different Self-Hosted Setups
Choosing between nzb360 and LunaSea is less about which app is objectively better and more about which one fits your current infrastructure and platform. Both are legitimate tools. The right answer depends on your device, your stack depth, and your openness to software that may eventually require migration.
Best Fit For Android-First Power Users
If your daily driver is Android and your home lab includes Plex, Jellyfin, or Emby alongside your Usenet automation stack, nzb360 is the cleaner single-app solution. Its integrations with Tautulli and the full *arr suite mean you rarely need to leave the app.
nzb360 also tracks queue status, history, and match outcomes per download item, which is genuinely useful for auditing your archival data pipeline over time.
Best Fit For Cross-Platform And FOSS-Oriented Users
LunaSea is the right choice if you use an iPhone or iPad and have no Android device in your workflow. It is also the better fit for builders who prioritize open source software and want an auditable codebase.
The archived status is a real consideration, not a dealbreaker. LunaSea works today and covers the core stack. The successor project will remain FOSS, so staying in that ecosystem is a reasonable long-term bet if you value the open source angle.
When To Consider Adjacent Tools And Ecosystem Add-Ons
A growing home lab often outgrows any single mobile app. Tools like Buildarr and Recyclarr handle configuration management for your *arr services programmatically, which reduces how often you need to touch the mobile app at all.
Ecosystem utilities like Unpackerr, Tdarr, Exportarr, Excludarr, Listrr, and Posterr handle specialized tasks at the automation layer. Request bots like Requestrr, Addarr, Doplarr, and Searcharr integrate with Discord or the Fediverse, letting you add items to Radarr without opening any mobile app at all.
Reiverr and Pulsarr add library management layers that pair well with Jellyfin or Emby stacks. For most users, nzb360 or LunaSea remains the daily driver, with these tools filling gaps at the edges.
For a reliable Usenet backend to power the stack both apps manage, Get Newshosting or Get Easynews are solid starting points with strong retention and SSL support.
Frequently Asked Questions
Which app offers better overall management for Sonarr, Radarr, and similar services?
nzb360 offers broader integration across the full Servarr ecosystem, including Readarr, Mylar3, and Whisparr in addition to Sonarr and Radarr. LunaSea covers the core trio well but its archived state means newer *arr services may not have current support. For Android users with deep stacks, nzb360 is the stronger option.
What are the main differences in features and supported integrations between the two apps?
nzb360 supports more services out of the box, including Tautulli, Plex, Jellyfin, Emby, and multiple simultaneous instances of each *arr service. LunaSea uses a profile-based system that handles multiple server environments cleanly but covers fewer total integrations. Both support SABnzbd, NZBGet, NZBHydra2, Sonarr, Radarr, and Lidarr.
How do the pricing models compare, including free tiers, one-time purchases, and subscriptions?
LunaSea is completely free in its current form with no feature restrictions. nzb360 has a limited free tier and a one-time premium unlock priced around $7.49 that removes all limitations. Neither app uses a subscription model, though LunaSea’s successor project may introduce paid app store distribution in the future.
Which option is more reliable and faster for remote access and notifications?
nzb360 is generally considered faster for loading service data and more reliable for push notifications based on community experience. Both apps perform well over a VPN-secured remote connection. LunaSea performs better on iOS hardware than on lower-end Android devices due to its Flutter framework.
Which app is easier to set up and use for beginners?
nzb360’s setup process is more explicit, with labeled configuration screens for each service that guide first-time users through entering server addresses, ports, and API keys. LunaSea’s profile system is powerful but adds an abstraction layer that can confuse beginners. For someone new to self-hosted tools, nzb360’s onboarding feels more approachable.
How well does each app handle security features like API keys, HTTPS, and reverse proxies?
Both apps store API keys locally on the device and support HTTPS connections through a reverse proxy. Neither transmits credentials to external servers. The security of your setup depends on your infrastructure: using SSL, placing authentication in front of exposed services, and routing remote access through a VPN are recommended practices for both apps regardless of which you choose.