Open-source project
binwiederhier/ntfy avatar
binwiederhier/ntfy

ntfy: Push notifications over plain HTTP, no app account required

Send push notifications to your phone or desktop using PUT/POST

35,571 stars1,717 forksGoApache-2.0

At a glance

What is it?
ntfy turns any PUT or POST request into a phone or desktop notification, with a free hosted service and a self-hostable Go server. It is a pragmatic choice for script and cron alerts, but you should weigh its open-topic model and self-hosting responsibilities.
Who is it for?
Adopt ntfy if you want a low-friction way to get script, cron, or CI notifications to your phone or desktop without creating accounts or paying per message. It is a poor fit if you need guaranteed delivery, end-to-end encrypted content, or strict access control, because the default hosted topics are public.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • binwiederhier/ntfy35,571 ★ · +1,979
Star history
Repository2026-08-182026-11-15
binwiederhier/ntfy33.6k35.6k

1,979 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What ntfy actually solves

ntfy solves a narrow but common problem: getting a notification from a script, cron job, or CI pipeline to a phone or desktop without signing up for a push service or writing a mobile app. The README states it is a simple HTTP-based pub-sub notification service. You send a PUT or POST to a topic, and any subscriber to that topic receives the message. The free public instance at ntfy.sh works without an account, and the server is open source so you can host your own. The target user is anyone who writes automation and wants a push channel that is as easy as curl. It is not a general-purpose messaging platform, nor does it attempt to be. The core value is the low barrier: no SDK, no registration, no fee for basic use.

Pub-sub over HTTP: the mechanism

The architecture is a classic publish-subscribe model, but the transport is plain HTTP. A publisher sends a request to a URL that encodes the topic name, like https://ntfy.sh/mytopic, and the server delivers it to the subscribers of that topic. Subscribers are the mobile apps or a desktop client. This design has a clear trade-off: the server must be reachable by both publishers and subscribers. If you self-host, you need a public endpoint or a VPN for your devices. For critical delivery, test how the service behaves when a subscriber is offline.

Getting started: commands and config

The README points to the documentation for getting started, but the core usage is visible in the project description: send a notification with a PUT or POST. A PUT or POST request to a topic is all it takes to publish. For self-hosting, the README links to an install guide, and the repository ships a Dockerfile and a docker-compose.yml. There is also an Android app available on Google Play and F-Droid, and an iOS app on the App Store, both open source. The repository's docker-compose.yml runs the image with the command serve and mounts /etc/ntfy for configuration. The public instance requires no setup; you just pick a topic name. That is the fastest path, but it comes with the caveat that anyone who guesses the topic name can read or send messages.

The public topic problem

The most obvious limitation is that ntfy.sh topics are public by default. The README says you can send notifications without signing up, which implies no authentication on the hosted service. Anyone who knows a topic name can subscribe to it or publish to it. That is acceptable for non-sensitive alerts like a build finished or a package updated. It is dangerous for anything that reveals internal information, like a server error log or a deployment IP. If you need privacy, check the documentation before sending anything sensitive. This is a real trade-off between zero-friction and security. For a hobbyist or a small team, the convenience may win. For a company handling sensitive data, it is a non-starter without additional work.

Self-hosting: what you take on

Running your own ntfy server is a way to control data and topic access, but it shifts the burden to you. The README says you can easily run your own instance and links an install guide. The repository ships a Dockerfile and a docker-compose.yml, but you still need a reachable endpoint and a way to keep the server running. You also need to manage TLS certificates and possibly a reverse proxy. The repository's recent releases, like v2.37.1, show active maintenance, which is a good sign, but you are responsible for upgrades. The Apache-2.0 license means you can modify and redistribute the code, but you must retain the license notices. The author offers paid plans for the hosted service. Self-hosting is a weekend project for a developer, but it is not a zero-ops solution.

Alternatives and the difference in approach

The main alternative to ntfy is a dedicated push notification service like Pushover or Gotify. Pushover is a hosted service and Gotify is a self-hosted server. ntfy's approach is more minimal: no account, just a topic name. That makes ntfy faster to adopt but less secure by default. If you need authentication out of the box, check whether those alternatives fit better. If you want the least friction and do not care about topic privacy, ntfy wins. The choice comes down to whether you trust the channel or want to control it from day one.

Maintenance and upgrade considerations

The project is actively maintained, with releases as recent as November 2026, so it is not abandoned. The Apache-2.0 license is permissive and business-friendly. For a self-hosted deployment, you will need to track releases and apply updates. The mobile apps are separate repositories, so you must update the server and the app independently. The hosted service is free, and the author offers paid plans starting at $5/month. For a production use case, you should verify the upgrade process and test it in a staging environment. The documentation site is the primary source for config details, and it is linked from the README. The maintenance cost is moderate: it is a single Go binary, so deployment is simple, but you still own the operational duties like backups and monitoring.

Editorial conclusion

Adopt ntfy if you want a low-friction way to get script, cron, or CI notifications to your phone or desktop without creating accounts or paying per message. It is a poor fit if you need guaranteed delivery, end-to-end encrypted content, or strict access control, because the default hosted topics are public. Before adopting, verify your delivery requirements, and test how the app behaves with your phone's battery optimization. For production alerts, pair ntfy with a reliable upstream monitor rather than relying on it as the sole channel.

Frequently asked questions

What is ntfy and what does it do?

ntfy, pronounced notify, is a simple HTTP-based pub-sub notification service. You can send notifications to your phone or desktop via scripts from any computer, without having to sign up or pay fees, and a free version is available at ntfy.sh with open source Android and iOS apps.

How much does ntfy cost to use?

The free version at ntfy.sh has no sign-up and no fees. The maintainer also offers paid ntfy Pro plans for anyone who would rather not self-host, for as low as $5 per month, and accepts donations through GitHub Sponsors and Liberapay.

Can ntfy be self-hosted?

Yes, the project is open source and the repository ships a Dockerfile, a Dockerfile-arm, a Dockerfile-build and a docker-compose.yml that runs the image binwiederhier/ntfy with the command serve, mounting /etc/ntfy for configuration and /var/cache/ntfy for its cache. Installation and self-hosting have their own section in the documentation at ntfy.sh/docs.

How do I get notifications from ntfy on iOS?

There is an open source iOS app published on the App Store, with beta builds distributed through TestFlight. The documentation has a dedicated Android/iOS section for subscribing on a phone, and release announcements go to the ntfy.sh/announcements topic on the hosted instance.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/binwiederhier-ntfy.svg)](https://hysenlabs.com/projects/binwiederhier-ntfy)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/binwiederhier-ntfy.svg)](https://hysenlabs.com/projects/binwiederhier-ntfy)

Was this useful?