Pushover

Best Self-hosted Alternatives to Pushover

A curated collection of the 3 best self hosted alternatives to Pushover.

API-first cloud service that delivers real-time push notifications to iOS, Android and desktop clients. Accepts API requests and integrations to send alerts, with device targeting, priority/expiry options and delivery receipts for app alerts, monitoring and automation.

Alternatives List

#1
ntfy

ntfy

ntfy is a lightweight HTTP pub-sub service to send push notifications to phones, desktops, and browsers via PUT/POST or a REST API.

ntfy screenshot

ntfy (pronounced “notify”) is a simple HTTP-based publish/subscribe notification service. It lets apps, servers, and scripts send push notifications to phones, desktops, and web browsers using straightforward HTTP requests.

Key Features

  • Publish messages to topics via HTTP PUT/POST
  • Topics are created dynamically by publishing or subscribing
  • Web app for browser subscriptions with desktop notifications
  • Push delivery to mobile clients (Android and iOS apps are available)
  • Works well for automation and server-to-user alerts without complex integrations

Use Cases

  • Send server and backup job notifications from shell scripts or cron jobs
  • Application alerting (deployments, monitoring events, CI results) via a simple REST-style interface
  • Personal notification hub for homelab events and device automation

Limitations and Considerations

  • If used without accounts/reserved topics, topic names function like shared secrets and should be hard to guess

ntfy is a pragmatic choice when you want a minimal, reliable notification pipeline based on plain HTTP. It is well-suited for automation scenarios and for teams or individuals who prefer a simple pub-sub model over heavy messaging platforms.

28.9kstars
1.2kforks
#2
Frigate-Notify

Frigate-Notify

Lightweight Go service that forwards events from a standalone Frigate NVR to Discord, Matrix, SMTP, webhooks and many services (via Apprise). Supports MQTT or direct API and Docker.

Frigate-Notify screenshot

Frigate-Notify is a lightweight Go application that forwards event notifications from a standalone Frigate NVR to a variety of notification endpoints. It can consume events via MQTT or directly from the Frigate API and dispatch alerts to many services either natively or through the Apprise API.

Key Features

  • Event ingestion via MQTT or direct Frigate API polling
  • Multiple notification outputs: Discord, Gotify, Matrix, Mattermost, Ntfy, Pushover, Signal, SMTP, Telegram, Webhook and many more via Apprise
  • Lightweight Go binary with official Docker image for easy deployment
  • YAML-based configuration with an example config file for mapping events to notification targets
  • Aliveness probe via HTTP GET to integrate with uptime/healthcheck tools
  • Designed for standalone Frigate installations; Home Assistant not required

Use Cases

  • Send instant alerts from a home or small-business Frigate NVR to chat apps and mobile push services
  • Integrate Frigate events into automation pipelines or incident workflows via webhooks or Apprise-backed endpoints
  • Monitor Frigate health using the built-in aliveness endpoint combined with uptime checks

Limitations and Considerations

  • Configuration is file-based (YAML); there is no built-in web UI for managing notification rules
  • Some notification channels rely on external services or the Apprise API, which may require additional setup or credentials

Frigate-Notify is suited for users who want a simple, container-friendly bridge from Frigate events to many notification endpoints. It emphasizes lightweight operation and wide integration coverage rather than a graphical management interface.

331stars
33forks
#3
TestFlight Watcher

TestFlight Watcher

Node.js utility that monitors TestFlight invite URLs and sends Pushover notifications when beta slots open; configurable via .env with an optional web endpoint for management.

TestFlight Watcher is a lightweight Node.js script that periodically checks TestFlight invite URLs for available beta slots and sends alerts via Pushover when openings are detected. It is driven by a simple configuration file and includes a minimal web endpoint for managing accepted invites.

Key Features

  • Periodic monitoring of one or more TestFlight invite URLs with configurable interval
  • Push notifications delivered via the Pushover API when a slot becomes available
  • Configuration driven via a .env file (user/app tokens, URLs, OTP secret, check interval, priority, port)
  • Built-in setup flow to create the .env and manage monitored URLs
  • Simple webserver endpoint to clear or manage already-accepted invites
  • Lightweight Node.js implementation with low memory and CPU requirements

Use Cases

  • Automatically alerting testers when public TestFlight invite slots become available
  • Maintaining and monitoring a list of TestFlight invite links for a team or community
  • Integrating slot-availability notifications into personal automation workflows

Limitations and Considerations

  • Requires a Pushover account and valid Pushover credentials to send notifications
  • Relies on scraping/public TestFlight page behavior and may break if Apple changes the page structure or invite flow
  • Not an official TestFlight API client; intended for monitoring public invite links only
  • Minimal web UI and management features; not designed for large-scale or enterprise monitoring
  • Requires Node.js (v12+) and appropriate environment configuration

TestFlight Watcher is suitable for hobbyists and small teams who want automated alerts for TestFlight availability. Its minimal footprint and straightforward configuration make it easy to run on small servers or personal machines.

17stars
0forks

Why choose an open source alternative?

  • Data ownership: Keep your data on your own servers
  • No vendor lock-in: Freedom to switch or modify at any time
  • Cost savings: Reduce or eliminate subscription fees
  • Transparency: Audit the code and know exactly what's running