Lert vs ntfy: which push notification tool is right for you?
ntfy and Lert both turn an HTTP request into a push notification on your phone — but they sit at opposite ends of the same spectrum. ntfy hands you an open-source engine you can run anywhere; Lert hands you a finished, hosted service with nothing to set up. Here's an honest look at which one fits you.
The short version
ntfy is a well-loved open-source pub/sub notification service. You publish a message to a named topic, and any device subscribed to that topic gets it. You can use the maintainers' hosted instance or run the whole thing yourself on your own server. It's cross-platform, scriptable, and beloved by people who like to own their stack.
Lert is a hosted, iOS-first service built around a single idea: the endpoint URL is the authentication. You install the app, copy your unique URL, POST to it, and your phone buzzes — no account, no API key, no topic to name, no SDK. It also ships an MCP server so AI assistants can notify you directly.
Neither is "better" in the abstract. They optimize for different things: ntfy for control and portability, Lert for zero-friction simplicity on iOS.
Side by side
| Lert | ntfy | |
|---|---|---|
| Model | Hosted, managed service | Open source; self-host or use hosted instance |
| Setup | Install app, copy URL, done | Subscribe to a topic (or stand up a server) |
| Auth | The endpoint URL is the auth | Topic name; optional tokens / access control |
| Platforms | iOS today (Android planned) | Android, iOS, web, desktop, CLI |
| Self-hosting | No | Yes — a core strength |
| AI / MCP | Ships an MCP server | Not built in; scriptable via HTTP |
| Pricing | Free tier; Pro $2.99/mo | Free to self-host; hosted tiers available |
Competitor details can change — check the ntfy site for current platforms, pricing, and features at the time you read this.
When to choose ntfy
Pick ntfy if any of these describe you:
- You want to self-host. This is ntfy's headline feature. If your alerts must stay inside your own infrastructure, or you simply prefer owning the server, ntfy is built for it and Lert can't match it.
- You value open source. The code is public, auditable, and forkable. For some teams that's non-negotiable, and it's a genuine, real advantage.
- You need broad platform coverage today. ntfy has Android, iOS, web, and desktop clients, plus a CLI. If your team is on Android or you want a browser to receive alerts, ntfy already does that.
- You like the pub/sub model. Topics let many devices subscribe to the same stream, which is a clean fit for team-wide or fan-out notifications.
When to choose Lert
Pick Lert if any of these describe you:
- You want zero setup. No server to run, no topic to name, no config to reason about. Install the app, copy one URL, and you're notifying yourself in under a minute.
- You want the URL to be the whole security model. There's no separate token or account to manage — you hold a secret URL, and you can regenerate it if it ever leaks. It's a simpler mental model for personal alerts.
- You're on iOS and want a polished native push. Lert is iOS-first, and the notification wakes a locked phone and buzzes a paired Apple Watch in about a second.
- You want AI assistants to notify you. Lert's built-in MCP server lets tools like Claude send you a push when a long task finishes, with no glue code.
Deciding factor: if "I don't want to run or configure anything" is your priority, Lert is the shorter road. If "I want to own and control the whole pipeline" is your priority, ntfy is the honest answer. Both send a great notification — they just ask different things of you first.
A fair conclusion
ntfy and Lert aren't really competing for the same person. ntfy is a superb choice for tinkerers, homelabbers, and teams who want an open, self-hostable, cross-platform notification bus — and its open-source nature is a real strength Lert deliberately doesn't try to replicate. Lert is a superb choice for people who want to skip all of that and just get a notification on their iPhone with a single POST and nothing to maintain. Choose based on which trade-off you'd rather live with: control, or the absence of setup. Either way, you end up with a phone that tells you when something happened.
FAQ
Is ntfy free?
ntfy is open source and free to self-host. It also offers a hosted instance with free and paid options. If you run your own server, your only cost is the infrastructure it runs on. Check the ntfy site for current hosted pricing.
Can I self-host Lert like ntfy?
No. Lert is a managed, hosted service — that's the trade-off. You get zero setup and no server to maintain, but you can't run it on your own infrastructure. If self-hosting is a hard requirement, ntfy is the better fit.
Does ntfy require an API key?
ntfy publishes to a topic by name and can optionally add access control with tokens or auth, especially on protected or self-hosted instances. Lert takes a different approach: your endpoint URL itself is the authentication, with no separate key or account.
Which is better for a beginner?
If you want the shortest path from zero to a buzzing phone with nothing to configure, Lert is designed for that. If you enjoy running your own infrastructure and want full control, ntfy rewards that.
Try the zero-setup side of the trade-off.
Download Lert, copy your URL, POST to it. If it's not for you, you've lost about a minute.