Server compatibility and push delivery

Use public or self-hosted ntfy servers with the same HTTP protocol.

NTF-AI is an independent iPhone and iPad client for ntfy, forked from the MIT-licensed ntfy iOS app. It is not affiliated with ntfy.sh or the ntfy project. Server and topic must match across the app and your scripts.

Public servers

The default server is ntf-ai.app, run by the app's publisher. ntfy-me.com is the same server, with the same topics and messages, so older links and scripts keep working. It accepts plain HTTP publishing without an account or API key. Pick a long random topic: anyone who knows the topic name can read and publish. See agent setup for a tested recipe.

ntfy.sh topics work when you open or refresh the app, but do not get instant banners in NTF-AI. ntfy.sh relays iOS push only to the official app. ntf-ai.app and a self-hosted server configured with its relay can send instant push to NTF-AI. Delivery still depends on connectivity and iOS settings.

A topic name belongs to one server. The same name on ntfy.sh and ntf-ai.app describes two separate topics; messages and history are not copied between them. Your existing clients and scripts can continue using whichever server you choose.

Your own ntfy server

Subscribe with your server's URL in the app. For instant push to NTF-AI, the server configuration is:

upstream-base-url: "https://ntfy-me.com"

Restart your server after editing its configuration. An ntfy server uses one upstream relay: changing this value affects which iOS app receives its instant push. An ntfy.sh relay serves the official iOS app; the ntfy-me.com relay serves NTF-AI. Do not change a shared server's relay without checking the needs of its users. Authentication and access rules remain your server's responsibility. See self-hosting.

Shared topics across clients

The official ntfy Android app and the web app can use the same server and topic. Ordinary HTTP action buttons and plain messages use the stock ntfy protocol. App-specific features such as encrypted-topic senders need compatible clients; do not assume every client supports them.

Existing app subscriptions

The app preserves existing subscriptions and settings when updated. Versions before 1.14 used a different default server; check each topic's server before changing a sender. Subscribing does not import another server's message history. Support covers delivery checks.