An ntfy-compatible alternative — hosted for you, or your own
TYO Notify speaks the same simple HTTP interface as ntfy. If a tool already knows how to send an ntfy notification — your monitoring, your automation, your scripts — it can send to TYO Notify by changing one address. No lock-in, no rewrite.
Switching is one line
Point your existing publisher at a TYO Notify broker:
# before (ntfy.sh) curl -d "backup done" https://ntfy.sh/my-alerts # after (TYO Notify — hosted) curl -d "backup done" https://freemq.tyo.com.au/notify/my-alerts # or your own broker curl -d "backup done" https://push.mycompany.com/notify/my-alerts
How it compares
| Capability | TYO Notify | ntfy | Pushover | Telegram bot |
|---|---|---|---|---|
| Publish with plain PUT / POST | Yes | Yes | Yes (via API) | No (bot API) |
| No account required | Yes | Yes | No | No |
| Hosted option | Yes (freemq) | Yes (ntfy.sh) | Yes | Yes |
| Self-host your own server | Yes | Yes | No | No |
| No ads, no analytics SDKs | Yes | Yes | Yes | Mixed |
| UnifiedPush (de-Googled) | Yes | Yes | No | No |
| Works with existing ntfy integrations | Yes | — | No | No |
ntfy is a well-loved open-source project — we don't try to out-open-source it. TYO Notify wins when you want the hosted convenience without the ads/account trade-offs elsewhere, one interface across a hosted or self-hosted broker, and TYO's support behind it.