Gotify vs ntfy: message model, credentials and what you end up running
One carries priority as an attribute, the other keeps the body as the message and moves the rest into headers.
3 min read
Gotify vs ntfy is a familiar argument in homelab circles, and the honest answer is that both are good and the deciding factor is rarely the software. It is whether you want a topic you can publish to from anything, or an application model with real message priorities on a server you control.
What each tool calls a message
| Field | ntfy | Gotify |
|---|---|---|
| Body text | The request body | content |
| Headline | A header | title |
| Urgency | A priority header | priority |
| Identity | The topic name | The application id |
| Timestamp | Set on arrival | creation date |
Gotify's documentation lists content, title, creation date, application id and priority as the message attributes. ntfy keeps the body as the message and moves the rest into headers. Both are clean, and both are narrow enough to learn in ten minutes.
Why people pick ntfy
The first notification is almost instant. Install the app, subscribe to a topic name, publish. There is a CLI, the app is on the major stores plus F-Droid, and the public service means no server is required to try it.
That last point cuts both ways. The public service is convenient, and the documentation warns that topic names are public, so the name must be unguessable. Self-hosting keeps that concern inside your own perimeter.
Why people pick Gotify
Gotify's model gives every sender its own application credential, so revoking one does not affect the others. It also carries a priority attribute, which lets an outage bypass quiet behaviour that a routine message should not.
The cost is that Gotify is self-hosted only. There is no public instance run by the project, so a server, a certificate and a route are prerequisites rather than options.
The option neither covers
Both are services you operate. If the reason you are comparing them is that you would rather not operate anything, the comparison is a detour.
AyePing runs the receiving side. You create a token in its app, store it as an environment secret, and POST to a username address. A text body is the title; a JSON body adds a message and a colored label. A success returns 202 with an id, and errors come back as codes such as 401 unauthorized or 402 quota_exhausted.
The trade is straightforward: you stop running a server, and you start paying a small subscription once the trial pings are gone.
Reliability questions to ask both
Who notices when the notification path dies? A monitor that fails silently is worse than a manual check, because you stop checking. Whatever you pick, add a heartbeat that complains when a successful send has not happened recently.
What happens on a retry? Both self-hosted tools will accept a duplicate POST. If your job retries, deduplicate on your side, or use a service with an idempotency header.
What does the phone show on a lock screen? A title of a few words. If the tool lets you set one, use it and put the host in it.
Cost, as of November 2026
Self-hosted ntfy and Gotify cost nothing in licence fees, whatever you pay for 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 Pro is $20 a month or $120 a year for 1,200,000 pings.
The short version
For a homelab with a reverse proxy, either self-hosted tool is a fine answer, and the choice comes down to whether you want topic-style publishing or application-style credentials. For a laptop and a handful of scripts, a hosted endpoint is less work and easier to keep alive.
FAQ
Do I need Docker for either tool?
Both are commonly deployed as containers, and both can run without Docker if you prefer a native install. Check each project's installation page for the current options.
Can I self-host ntfy and still use the mobile app?
Yes. The app can point at your own server instead of the public one.
Is Gotify available as a hosted service?
Gotify's documentation covers running your own server. There is no project-run public instance described in the pages above.
FAQ
Do I need Docker for either tool?
Both are commonly deployed as containers, and both can run without Docker if you prefer a native install. Check each project's installation page for the current options.
Can I self-host ntfy and still use the mobile app?
Yes. The app can point at your own server instead of the public one.
Is Gotify available as a hosted service?
Gotify's documentation covers running your own server. There is no project-run public instance described in the pages above.
Originally published on claudegpt.si