ntfy

ntfy is an open-source push notification service that lets scripts and applications send alerts to phones or desktops through simple HTTP PUT or POST requests. Self-hosting the ntfy server gives a homelab or private infrastructure control over topics, authentication, message history, attachments, and delivery configuration.

Why people choose ntfy

The useful alternative intent is usually “self-hosted Pushbullet or Pushover alternative” rather than the brand name alone. ntfy keeps the publishing interface simple while offering mobile apps, a web UI, CLI access, topic subscriptions, priorities, tags, action buttons, and message attachments.

What is included

The official docs cover a statically linked server, Docker image and packages for amd64, armv7, and arm64, HTTP publishing and subscribing, Android/iOS apps, a web interface, access control, message caching, attachments, web push, SMTP publishing, Firebase delivery for the public service, and Prometheus metrics.

Requirements and tradeoffs

A basic server can run as one ntfy process with file-backed cache and attachment storage; PostgreSQL is an optional configuration for deployments that need it. You must choose a public base URL, protect topics with authentication and access rules, persist cache and attachment data, and use TLS or a correctly configured reverse proxy. Topic names are public by default on the public service, so do not treat an unprotected topic as a private channel.

Best fit

Choose ntfy when you need lightweight alerts from backups, monitoring, scripts, or home automation without adopting a larger notification platform. If you need guaranteed mobile delivery semantics, complex workflow orchestration, or a managed service with no operational work, compare it with hosted providers or a broader automation stack.