← Directory

Notifiarr

Notifiarr is a self-hosted client for the Notifiarr notification service, giving homelab users unified alerts, media requests, health checks, and scheduled…

  • Communication
  • Media Applications
  • Other
  • Productivity
  • Tools & Utilities
Notifiarr is a self-hosted client for the Notifiarr notification service, giving homelab users unified alerts, media requests, health checks, and scheduled reports across Radarr, Sonarr, Plex, and download applications.

Platform availability

Available on 4 of 9 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
93last commit 19 days ago
Popular
59938 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
100256 MB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
938
Open issues
22
Last commit
2026-09-25
Latest release
v0.9.7
License
MIT
Activity
declining

Checked 7 days ago - source: GitHub (Notifiarr/notifiarr)

Resources & Compatibility

Minimum requirements: 256 MB RAM, 1 CPU core(s), 1 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 16 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start from the example config file Use the provided example configuration file as your starting point and edit it for the notification services you actually use. It is where Notifiarr learns where and how to send alerts, so leaving it empty or missing means it has nowhere to send notifications. source
  • Unraid installation settings After installation, open the web UI on port 5454, use a privileged container for system drive reporting, and mount extra paths to report drive space. source

Fetched 7 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What port-forwarding issue did a user mention in a Docker thread about Notifiarr?

A user described getting stuck on a port-forwarding step while setting up Discord notifications for containers.

Can Notifiarr copy settings from Trash Guides?

Yes, one user understood that Notifiarr can copy Trash Guides settings in one click, which they preferred because the Trash Guides instructions felt intimidating.

Can Notifiarr collect notifications from multiple services and send them to one target?

The source describes a common Notifiarr-style use case where notifications from apps and services such as *arr tools, Synology, or promos are collected and sent to one target like Discord.

What Plex and starr-related capabilities are listed in the Notifiarr client README?

The README lists scheduled Plex session and finished-watching notifications, automated Plex trash emptying, Radarr/Sonarr library syncing, and backup corruption checks.

Where does the Notifiarr project point for installation, configuration, and troubleshooting?

The README points to a wiki with install instructions, and separate wiki pages for configuration and troubleshooting.

Answers sourced from github.com, www.reddit.com, www.reddit.com, www.redditmedia.com

Community

Collected 16 days ago - public community threads