Ntfy
Lightweight push notification service for scripts, servers and applications, usable from HTTP, CLI, web or mobile.
Overview
Ntfy lets you send notifications from a script, server, application or automation tool, then receive them in a web interface, mobile app or compatible client. The service is based on ntfy and is useful for simple alerts without deploying a heavy notification platform.
It keeps the model simple: publish a message to a topic and subscribe to that topic from another device or tool. This makes it practical for technical alerts, small automations and lightweight personal monitoring, especially when you want something faster to wire up than a full monitoring stack.
Quick facts
| Service URL | ntfy.hostux.net |
|---|---|
| Service type | Notifications and push alerts |
| Free software used | ntfy |
| Type of operation | Publish / subscribe by topic |
| Project website | ntfy.sh |
| Source code | github.com/binwiederhier/ntfy |
| Account required | No for simple use on open topics, depending on service configuration |
Why use Ntfy
- Send an alert from a script, a scheduled task or a server.
- Receive a notification quickly on a phone, the web or a workstation.
- Set up lightweight monitoring without deploying a heavy solution.
- Add notifications to a technical workflow with a few HTTP commands.
- Keep a system simple, readable and easy to integrate into automations or homelab tooling.
For many everyday cases, that simplicity is the main benefit: you can start with one topic and a single curl command, then expand only if the workflow proves useful.
Main features
- Publish messages through HTTP
PUTorPOSTrequests. - Subscribe to a topic from the web, a mobile app, a CLI client or an API.
- Subscription formats in JSON stream, SSE, raw text or WebSocket.
- Message options such as title, priority, tags or other useful metadata.
- Possible support for extra functions depending on server configuration, such as attachments or topic protection.
How the service works
- You pick a topic, which acts as a notification channel.
- You publish a message to that topic with an HTTP request or via the ntfy client.
- Subscribers to the topic then receive the notification on the web, on mobile or via a subscription API.
- On an open service, the topic effectively acts as a secret: it is best to choose a name that is hard to guess.
- Depending on the instance configuration, some topics may also be protected by authentication or access rules.
Use cases
- Alert at the end of a backup, an update or a cron job.
- Notify a simple incident or a state change on a server.
- Receive a message from a shell script, an application or a CI/CD pipeline.
- Track technical events without deploying a full monitoring stack.
- Connect notifications quickly to a personal service, a homelab or a small operations workflow.
It also fits well for personal operational comfort: being warned that a long-running task finished is often enough, even if you do not need full historical dashboards.
Usage examples
Ntfy can be used very simply from a script, terminal or application. The principle stays the same: publish a message to a topic, then subscribe to it from the client of your choice.
curl -d "Backup completed" https://ntfy.hostux.net/my-topiccurl -H "Title: Backup" -H "Priority: high" -d "Backup failed" https://ntfy.hostux.net/my-topicntfy publish my-topic "Deployment finished"curl -s https://ntfy.hostux.net/my-topic/jsoncurl -s https://ntfy.hostux.net/my-topic/sse
This service integrates well with uses such as backup notifications, scheduled-task alerts, change detection on a website or messages sent by an automation tool.
The ntfy ecosystem also documents concrete integrations with tools like Changedetection.io, Watchtower, GitHub Actions, Node-RED, Home Assistant or Uptime Kuma, depending on your usage.
Access the service
Service: ntfy.hostux.net