Hook.Notifier alternatives, compared
There are a few ways to send yourself a push notification. Here is an honest look at how the popular ones compare, and where Hook.Notifier fits: free, hosted, nothing to run.
| Option | Hosted | Free | What you set up |
|---|---|---|---|
| Hook.Notifier | Yes | Yes | Nothing to build |
| Pushover | Yes | No, one-time per platform | Nothing to build |
| ntfy | Self-host, or paid tiers | Free if self-hosted | Run a server (self-host) |
| Telegram / Discord bot | Yes | Yes | Bot, token, chat setup |
| Firebase (FCM) | Yes | Free tier | Project, tokens, backend, app |
| Build your own app | You host it | Your cost | Weeks of work |
The power features, compared
Beyond the basic ping, here is what each service can actually do with a notification.
| Feature | Hook.Notifier | Pushover | ntfy |
|---|---|---|---|
| Priorities | Yes, 4 levels | Yes, 5 levels | Yes, 5 levels |
| Quiet hours | Yes, server-side | Yes | Per-topic settings |
| Action buttons | Yes, up to 3 | No, one link | Yes, up to 3 |
| Scheduled delivery | Yes, up to 3 days | No | Yes, up to 3 days |
| Markdown | Yes | HTML subset | Yes |
| Update a sent notification | Yes, by id | No | No |
| Webhook payload templates | Yes, per hook in the UI | No | Yes, server config |
| Outgoing webhooks | Yes | No | No |
| Inbox with search and read state | Yes | History only | History only |
Read the full comparison
Push notifications without Firebase
Firebase is the default answer, and a real project on its own. Here is how to skip it entirely.
Stop rigging Telegram and Discord bots
A bot is a lot of plumbing to land a message in a chat app. Here is the simpler, native way.
A free alternative to Pushover
Pushover does the job well but is paid. Here is the free way to get the same result, plus an inbox.
Like ntfy, but without the self-hosting
ntfy is free if you self-host, and its hosted tiers are paid. Here is a hosted, free path with nothing to run.