Ntfy
Simple pub/sub notification service via HTTP.
Open the official app on ntfy.sh
This tool is hosted by its maintainers. Click below to open ntfy.sh in a new tab — it's their official demo.
Browse developer tools →What's next with Ntfy?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Ntfy?
Ntfy is an open-source HTTP-based pub-sub notification service that enables users to send push notifications to mobile devices or desktops via simple API calls. Developed under the Apache-2.0 license, it serves developers, system administrators, and automation engineers who need real-time alerts without complex infrastructure. The tool addresses the challenge of delivering timely notifications across devices by abstracting the complexities of push notification protocols. By using topics as temporary passwords, users can trigger alerts from scripts, command-line tools, or applications without requiring account sign-ups. Its lightweight design and flexibility make it ideal for integrating with CI/CD pipelines, monitoring systems, and custom workflows where immediate user feedback is critical.
How it works
Ntfy operates as a decentralized notification hub, allowing users to publish messages to specific topics and subscribe to receive alerts on their devices. Notifications are delivered via HTTP PUT/POST requests, making it accessible through standard web tools. The service prioritizes simplicity and accessibility, enabling users to send alerts without infrastructure overhead. Its core purpose is to bridge the gap between automated processes and human oversight by delivering actionable updates instantly. Ntfy supports rich notification features including priority levels (which affect sound/vibration patterns), action buttons, emojis, tags, and attachments. For example, a backup script can send a 'Backup successful 😀' message with a high-priority alert to a user's phone.
How to use it
- 1Create a topic by publishing a message to ntfy.sh/yourtopic (e.g., curl -d 'Alert' ntfy.sh/mytopic). This acts as a temporary password for subscriptions.
- 2Subscribe to the topic via the web interface, mobile app, or API to receive notifications. For example, a script can use curl -d 'Backup complete' ntfy.sh/mytopic to trigger an alert.
- 3Customize notifications with priority levels, emojis, or action buttons by appending parameters to the request (e.g., curl -d 'Error! ⚠️' ntfy.sh/mytopic?priority=high).
- 4Use the ntfy CLI tool for streamlined command-line interactions, such as ntfy pub mytopic 'System reboot' --priority high.
What it can do
- notifications
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/binwiederhier/ntfy
- license: Apache-2.0 — free to use
- privacy: Self-hosted — you control your data
Limitations
- Topics created without sign-up are temporary and may expire if unused
- Lack of advanced scheduling or persistent notification history
- Limited support for custom notification payloads compared to commercial services
- Requires public internet access for both publishing and subscribing
- No built-in authentication for non-Pro users beyond topic passwords
Understanding the result
Simple pub/sub notification service via HTTP.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (Apache-2.0).
- Built with
- (binwiederhier/ntfy)
- License
- Apache-2.0
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with binwiederhier/ntfy. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- Apache-2.0
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- Apache-2.0 License
Upstream project
Frequently asked
How does Ntfy handle notification delivery reliability?
Ntfy relies on HTTP/HTTPS protocols for message delivery, which may result in delivery delays or failures under network congestion. The service does not guarantee delivery or persistence of notifications, making it unsuitable for mission-critical systems requiring guaranteed delivery.
How does the topic-based subscription system work?
Users create topics by publishing any message to a unique URL (e.g., ntfy.sh/mytopic). Subscribers must use the same URL to receive messages. Topics are ephemeral by default, meaning they expire after a period of inactivity unless upgraded to Pro. This system avoids requiring user accounts but exposes topics to potential guessing attacks if not properly secured.
How do I send a notification from a Python script?
Use the requests library to send a POST request: import requests; requests.post('https://ntfy.sh/mytopic', data='Script completed ✅'). Add parameters like ?priority=high or &tags=urgent to customize the notification. Ensure the script has internet access and proper error handling for failed deliveries.
How does Ntfy compare to Pushover or Firebase Cloud Messaging?
Ntfy differs from Pushover by using HTTP/HTTPS instead of its own proprietary API and requiring no account setup. Compared to Firebase Cloud Messaging, Ntfy lacks enterprise-grade features like device-specific targeting, message retention, and analytics. It excels in simplicity and ease of integration for lightweight use cases.
What should I do if I get a 403 Forbidden error?
A 403 error indicates the topic URL is incorrect or the subscription is invalid. Verify the topic URL matches exactly what was used for publishing. If using a Pro subscription, ensure the reserved topic name is correctly formatted. Temporarily generated topics may expire if not accessed within 24 hours.