ntfy Self-Hosted Push Notification Server

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

## Why This AMI Instead of a Manual Install

Deploying ntfy from scratch means installing Go dependencies, configuring nginx as a reverse proxy, hardening access control, generating credentials, and tuning SQLite - easily an afternoon of work for an experienced engineer. This AMI delivers all of that pre-configured so you can send your first push notification within minutes of launching an EC2 instance. You skip the setup toil and go straight to integrating notifications into your workflows.

## What ntfy Does

ntfy (pronounced notify) is a self-hosted pub/sub notification service. Publish a message to a topic with a single HTTP POST from any script, server, or application, and receive it in real time via the web app, the official Android and iOS apps, or any subscriber. All message data stays on your instance - nothing routes through third-party servers - making it a privacy-respecting replacement for hosted push services like Pushover or Firebase Cloud Messaging.

The current release available is ntfy 2.24.

## Example Use Case: CI/CD Deployment Alerts

1. Your CI pipeline completes a production deploy.

2. A single curl POST sends a status message to an ntfy topic on your instance.

3. On-call engineers receive the alert instantly on their phones via the ntfy mobile app.

No external SaaS dependency, no data leaving your VPC, and no per-message fees.

## Application Stack

• ntfy server - a single Go binary serving both the REST API and the web UI, binding to the loopback interface.
• nginx - reverse proxy handling TLS termination and forwarding requests to ntfy.
• SQLite - embedded database for accounts and the message cache. Zero external database cost or management overhead.

Because the entire stack runs in a single instance with minimal resource requirements, ntfy operates comfortably on smaller instance types, keeping infrastructure costs low.

## Secure By Default

• Access control defaults to deny-all; only authenticated users can read or publish.
• On first boot, a one-shot service creates a fresh authentication database and generates a unique administrator password stored in a root-only file.
• No shared or default credentials ship in the image.

This means you avoid the common risk of community images shipping with exposed default passwords.

## Ready To Use

Sign in as the administrator, create topics and access tokens, and start publishing with a single curl call. Subscribe in the web app or connect the official mobile apps to receive notifications in real time. Point a domain at your instance and configure TLS via nginx for production use.

## Get Started

To explore the product before committing to a larger deployment, launch on a small instance type and confirm end-to-end notification delivery. When ready, scale to a larger instance for higher throughput.

For a guided setup walkthrough or help integrating ntfy into your environment, contact cloudimg support at any time.

## cloudimg Support

24/7 technical support by email and live chat for deployment, upgrades, integrations, TLS termination, and access control configuration. Critical issues receive a one-hour average response time.

ntfy is a trademark of its respective owner. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.