Helmarr Supported Services: What Each Integration Does
Helmarr is a native iOS, iPadOS, and macOS client for self-hosted media stacks. This guide explains what each Helmarr supported service does as of June 2026, so you know which integration handles library automation, indexer management, downloads, media requests, playback analytics, or server administration.
How the stack fits together
A typical self-hosted media stack has separate jobs. Sonarr, Radarr, and Lidarr decide what should exist in the library. Prowlarr, NZBHydra2, and Jackett connect those managers to indexers and trackers. qBittorrent, Transmission, Deluge, SABnzbd, and NZBGet transfer files. Seerr, Overseerr, Jellyseerr, and Wizarr handle user requests or onboarding. Plex, Tautulli, Jellystat, Tracearr, Unraid, SSH, and SFTP expose runtime state, playback state, host state, or direct admin access.
Sonarr
Sonarr’s job is TV episode automation. It tracks series and seasons, applies quality profiles, searches Usenet or torrent indexers, sends matching releases to a download client, then imports and organizes completed files into a TV library.
Radarr
Radarr’s job is movie automation. It tracks wanted films, monitors availability, applies quality and custom format rules, pushes matching releases to download clients, and keeps movie files named and organized for media servers like Plex, Jellyfin, or Emby.
Lidarr
Lidarr’s job is music library automation. It tracks artists and albums, uses MusicBrainz style metadata concepts, searches configured sources, sends downloads to a client, and organizes audio files into a structured music collection.
Bazarr
Bazarr’s job is subtitle automation. It connects to Sonarr and Radarr, detects missing subtitle files, searches configured subtitle providers, downloads matching subtitles, and keeps subtitle files aligned with the media files your server is already using.
Prowlarr
Prowlarr’s job is indexer management. It centralizes torrent tracker and Usenet indexer configuration, then syncs those indexers into apps like Sonarr, Radarr, and Lidarr so every media manager does not need separate indexer setup.
NZBHydra2
NZBHydra2’s job is Usenet meta search. It aggregates multiple Newznab indexers and Torznab trackers behind one search interface, tracks indexer response and usage, and can give automation tools one consolidated indexer endpoint.
Jackett
Jackett’s job is torrent tracker translation. It acts as an API proxy that turns app requests from Sonarr, Radarr, Lidarr, qBittorrent, and similar tools into tracker-specific queries, then returns results in automation-friendly formats.
qBittorrent
qBittorrent’s job is torrent transfer control. It handles magnet links and torrent files, manages peers, trackers, priorities, categories, tags, speed limits, and seeding behavior, and exposes a Web UI that automation tools can control.
Transmission
Transmission’s job is lightweight BitTorrent downloading. It runs well on servers, NAS devices, and containers, exposes a remote interface, and gives the stack a simple torrent client for adding, pausing, removing, and monitoring transfers.
Deluge
Deluge’s job is plugin-friendly BitTorrent downloading. It separates the daemon from the interface, supports remote control, and is often used when users want a configurable torrent client with a server process that runs independently from the UI.
SABnzbd
SABnzbd’s job is Usenet downloading. It consumes NZB files, connects to Usenet servers, downloads binary articles, repairs and extracts completed jobs, and provides a queue that Sonarr, Radarr, Lidarr, or manual workflows can manage.
NZBGet
NZBGet’s job is efficient Usenet downloading. It retrieves articles from Usenet using NZB files, runs well on low-power servers, and focuses on fast queue processing, post-processing, and automation through its web interface and API.
Overseerr
Overseerr’s job is Plex-focused media requests. It gives users a request and discovery interface for movies and TV shows, then sends approved requests to Radarr or Sonarr so the automation stack can fetch the content.
Jellyseerr
Jellyseerr’s job is request management for Jellyfin and Emby users who want an Overseerr-style workflow. It lets users discover media, submit requests, and route approved movies or shows into Radarr and Sonarr.
Seerr
Seerr’s job is unified request management for Plex, Jellyfin, and Emby. It combines media discovery, user login integration, request approval, and Sonarr or Radarr handoff into one request layer for mixed media-server environments.
Tautulli
Tautulli’s job is Plex monitoring and analytics. It tracks current Plex activity, stream history, users, devices, libraries, bandwidth, and notifications so administrators can understand how their Plex server is being used.
Jellystat
Jellystat’s job is Jellyfin statistics. It records playback activity, user history, library usage, and server analytics for Jellyfin installations that need a dedicated reporting layer similar to Tautulli for Plex.
Tracearr
Tracearr’s job is playback monitoring and account-sharing detection across Plex, Jellyfin, and Emby. It analyzes stream access, user trust, violations, and historical playback patterns so administrators can spot unusual sharing behavior.
Plex
Plex’s job is media serving and playback. Plex Media Server indexes local media libraries, adds metadata, tracks active streams, and serves movies, TV, music, and photos to client apps. Helmarr’s Plex integration focuses on now-playing visibility and stream details.
Wizarr
Wizarr’s job is user onboarding. It creates invitation links for Plex, Jellyfin, Emby, and related services, then guides new users through account access, app installation, and request-system setup without requiring a manual admin walkthrough.
Unraid
Unraid’s job is host and storage management. It is a NAS operating system, application server, and virtual machine host. In a media stack, it often runs Docker containers, manages disks and shares, and exposes server health data that Helmarr can monitor.
SSH and SFTP
SSH and SFTP’s job is direct server access. SSH provides command execution and host-level administration, while SFTP provides file browsing and editing over the same secure transport family. In Helmarr, this is infrastructure control, not media automation.
The practical split
If you are planning a Helmarr setup from scratch, think in layers. Use Sonarr, Radarr, and Lidarr for library decisions. Use Prowlarr, NZBHydra2, or Jackett for search/indexer access. Use qBittorrent, Transmission, Deluge, SABnzbd, or NZBGet for transfers. Use Seerr, Overseerr, Jellyseerr, or Wizarr for user-facing requests and invites. Use Plex, Tautulli, Jellystat, Tracearr, Unraid, SSH, and SFTP for playback visibility, analytics, and server control.