Hosted ntfy: managed push notification hosting for people who want their scripts, servers, and apps to tap them on the shoulder.

Early Access

This app is a brand-new addition to ElfHosted, and is considered beta. It runs, we test it, and your trial lets you prove it fits before you commit, but our support team does not yet have deep experience with it. Expect some trial and error: lean on the upstream documentation, experiment freely, and share what you learn in Discord, where the community and team are figuring these new apps out together. If you need a battle-tested workflow today, our established apps are the safer pick.

What is ntfy?

ntfy (pronounced "notify") is a pub-sub push notification service. Publish a message to a topic with a plain HTTP PUT or POST (even just curl), and every device subscribed to that topic gets a push notification instantly. No vendor SDKs, no signup flows, no per-message fees.

It is the missing notification layer for everything else you run: backup scripts, cron jobs, Radarr and Sonarr, Uptime Kuma, Home Assistant, or anything else that can make an HTTP request. Messages support titles, priorities, tags, attachments, action buttons, and scheduled delivery.

Key Features

• Notifications via plain HTTP: One curl command sends a push to every subscribed device, from any script or app.
• Official Android and iOS apps: Both connect directly to your instance URL, so iPhone users get first-class push too.
• Locked down by default: Your instance ships deny-all, so nobody can publish to or snoop on your topics without an account you created.
• Rich messages: Titles, priorities, emoji tags, attachments, action buttons, and delayed delivery.
• Per-topic permissions: Manage users and fine-grained topic access from inside the app.
• Works with Apprise and webhooks: Most tools with webhook or Apprise support can target ntfy directly.

ntfy in Your Stack

ntfy is the alerting glue for an ElfHosted subscription: point Radarr and Sonarr notifications at it, have Warracker send warranty expiry alerts through it via Apprise, and let Uptime Kuma or your own cron jobs ping your phone the moment something needs attention.

If you already run Gotify, ntfy is the natural next step: the same idea, with an official iOS app.

Why Run ntfy on ElfHosted?

A notification service is only useful if it is always up. ElfHosted keeps your instance running, updated, and reachable from your phone wherever you are.

• Managed access and support: Provisioned in minutes, kept current, with humans on Discord when you need a hand.
• Plays well with other ElfHosted apps: Radarr, Sonarr, Warracker, and friends can all notify through it on the internal network.
• Persistent config: Users, access rules, and cached messages survive restarts and upgrades.
• Simple subscription: One flat monthly price with a 7-day trial, cancel anytime.

Works With

• Radarr / Sonarr: Grab and import notifications straight to your phone.
• Warracker: Warranty expiry alerts via Apprise.
• Uptime Kuma: Downtime alerts pushed instantly.
• Home Assistant: Automations that reach your pocket.
• Your own scripts: Anything that can curl can notify you.

Frequently Asked Questions

How do the mobile apps connect to my instance?
The official Android and iOS apps connect directly to your instance URL: set your instance as the default server in the app, sign in with the ntfy user you created, and subscribe to your topics. Your instance handles its own authentication, so mobile push works without any extra sign-on steps.

Is my instance private?
Yes. It ships with deny-all access, so no topic can be read or published without an account. You manage users and per-topic permissions inside the app.

Does ntfy support iPhones?
Yes, there is an official iOS app, which is the main reason many people choose ntfy over Gotify.

What can send notifications through ntfy?
Anything that can make an HTTP request: shell scripts, cron jobs, CI pipelines, and most apps with webhook or Apprise support, including much of the ElfHosted catalog.