Managed ntfy hosting

No. Your server runs with access control on and every topic closed by default. Without signing in with a user name and password or an access token, nobody can publish, subscribe or read anything, and nobody can sign up for an account. Only the web app page itself and a few status endpoints are public. A user you create can use only the topics you give that user.

Your app page shows the admin user name and a password generated for you. Sign in to the web app with them. Open Account in the web app to create access tokens for your scripts and phones. To add more users, call the admin API with your admin login: curl -u ADMIN:PASSWORD -X POST -d '{"username":"alice","password":"a long password"}' https://YOUR-APP/v1/users, then give that user a topic with curl -u ADMIN:PASSWORD -X PUT -d '{"username":"alice","topic":"alerts","permission":"read-write"}' https://YOUR-APP/v1/users/access. A user with no grants can do nothing. To change the admin password, set a new one in the app settings on CoreHost and restart.

Stop your old ntfy so its database files are complete. Copy user.db (your users, access rules and tokens), cache.db (your messages) and the attachment folder from the places your server.yml names under auth-file, cache-file and attachment-cache-dir. Create your ntfy app on CoreHost, wait until it is running and stop it from its page. Connect over SFTP with the details on the app page and upload user.db and cache.db to the top folder, replacing the ones there, and the attachments into the folder named attachments. Start the app. Your old users sign in with their old passwords and your access tokens keep working, with your messages in place. Your server.yml is not needed, because the settings on the app page replace it. Then point your phone apps and scripts at your new address.

Three things. Rules that let anonymous clients in are removed every time the app starts, so give scripts a user or an access token instead. A user with no access rule has no access at all, even if your old server was open by default, so grant each user the topics it needs. And if you already have a user named like our admin account, yours keeps its own password and ours gets the same name with -corehost added. We run the latest stable ntfy and update it for you; copy the files from the same release or an older one.

They solve the same problem from different ecosystems, and they complement each other. Gotify issues a token per application and pairs with its Android app. ntfy is topic based publish and subscribe with official apps for Android and iPhone, and richer messages with action buttons and attachments. If you are on iPhone, pick ntfy; plenty of people run both.

Not on CoreHost for now. UnifiedPush senders such as a Matrix server push to your server without a login, and your ntfy is closed to anyone who is not signed in, which is what keeps it private. If you need UnifiedPush, tell us in a support ticket.

Yes. The official ntfy app is on the App Store and Google Play. For instant delivery to iPhones, a self-hosted server sends a wake-up signal through the relay run by the ntfy project at ntfy.sh. It carries a hash of the topic and the message id, never the message. You can turn the relay off in the app settings if nobody uses an iPhone. Android delivery is direct and needs no relay.

We do. Curated updates roll out shortly after upstream releases and are tested on our platform first; security fixes move fast. If an update changes behaviour in a breaking way, we email you before it lands.

Take a final export or SFTP copy any time before you cancel. After termination we keep your data for 14 days (in case you change your mind), then purge it, backups included.

Yes. Point a CNAME at your instance, prove ownership with a TXT record, and TLS certificates are issued automatically. Cloudflare-proxied domains work; if you use CAA records, allow letsencrypt.org.