AI Tools
Which is better, ntfy or Gotify? A direct answer by setup
Gotify for credentials and priority on a server you run. ntfy for the shortest path to a first alert.
Which is better, ntfy or Gotify? For most people who already run a server, Gotify is the better fit when per-sender credentials and message priority matter, and ntfy is the better fit when you want the shortest possible publish path and do not mind a public topic name. If you do not want to run a server at all, both are the wrong answer and a hosted push endpoint is simpler.
The direct comparison
| Criterion | ntfy | Gotify |
|---|---|---|
| Server required | Only for self-hosting; a public service exists | Yes |
| Credential per sender | Depends on access rules | One application token each |
| Message priority | Header | Attribute |
| Mobile app | Android, iOS and desktop | Client app for the Gotify server |
| First setup | Under a minute with the public service | Install, configure, connect |
| Cost | Free self-hosted, Pro for hosted | Free self-hosted |
There is no single winner, only a winner for a given setup.
Choose Gotify if
- You already run a reverse proxy and a certificate pipeline.
- Several machines publish to one phone and you want to revoke one without touching the rest.
- Priority needs to change delivery behaviour, not just the wording.
- Payloads must stay inside your network.
Gotify's documentation is explicit about the model: applications only send, clients receive, and messages carry content, title, creation date, application id and priority. That clarity is why teams trust it with production alerts.
Choose ntfy if
- You want a working alert today, before provisioning anything.
- A topic-style address is acceptable, and you will pick an unguessable name.
- You prefer a body-is-the-message model with headers for the rest.
- You might move between the public service and self-hosting later.
ntfy's own guide warns that topic names are public, which is the one thing to internalise before using the public service for anything with a hostname in it.
Choose neither if
The comparison assumes you are willing to operate or trust a notification service. If the goal is a single request from a script to a phone, with no server and no topic to name, a hosted endpoint is less work.
AyePing issues a token in its free app, and a POST to https://ayeping.com/@username with a bearer token delivers the message. The body is a title of 1 to 100 characters, plus an optional Markdown message up to 2,000 characters and a colored label. A success returns 202 with a ping id.
Self-hosting still wins on one point that no hosted service can match: the payload never leaves your network.
A note on priorities
Priority is the feature most often cited when someone defends Gotify, and it is a real difference. If an alert must wake someone at 3am, test the behaviour on the actual phone before you commit. A colored label is not the same as a delivery priority, and neither is a documented level until your device respects it.
Costs, as of November 2026
Both self-hosted tools cost nothing in licence fees, plus your hosting. AyePing's trial gives 5 pings and 3 tokens with no card; Hobby is $8 a month or $49 a year for 120,000 pings and 25 tokens; Pro is $20 a month or $120 a year for 1,200,000 pings and 100 tokens.
The answer in one line
Run a server already? Gotify for credentials and priority, ntfy for speed of setup. Not running one? Use a hosted endpoint and stop comparing servers.
FAQ
Can I try ntfy without installing anything?
You need the mobile app to receive, but nothing to send beyond an HTTP client. The public service accepts a POST with no server of your own.
Does Gotify have a hosted option?
Its documentation describes running your own server. The pages above do not describe a project-run public instance.
Which is more secure for a public topic?
Neither is secure by default if the address is guessable. Pick a long random name, or self-host and control access at the server.