Ntfy

ntfy is an open-source HTTP-based push notification service built on a publish-subscribe topic model — agents POST to a topic URL, and all subscribed clients (phone apps, browser, CLI) receive the notification instantly. The zero-friction design stands out: the public ntfy.sh server requires no account for basic use, making it trivially easy to wire agent notifications without provisioning credentials. Self-hosting is straightforward for teams that need private notification infrastructure.

The API is HTTP-first and minimal: POST a message body to `https://ntfy.sh/<topic>` (or self-hosted equivalent) to deliver a notification. Headers control title, priority, tags, actions, and attachments. The simplicity is the feature — agents don't need SDKs or auth tokens to start delivering notifications for non-sensitive use cases. Access control is available through self-hosted deployments for scenarios requiring authentication.

Authentication is optional on the public server (topics are effectively public unless on a self-hosted instance with access control). For agents sending sensitive operational information, self-hosting with access controls or using topic names with sufficient entropy for obscurity is recommended. Self-hosted deployments support user management and topic access policies.

Reliability for the public ntfy.sh server is community-supported; teams building production agent alerting on the public server should evaluate SLA acceptability. Self-hosted deployments have full reliability control. The protocol itself is simple and robust — even on resource-constrained infrastructure, ntfy servers handle high message volumes efficiently.

Documentation is excellent and thorough. The self-hosting guide, access control documentation, and full API reference are well-written and reflect the project's engineering quality. Teams evaluating ntfy for agent notification infrastructure will find the documentation covers both simple usage and advanced configuration clearly.