Head to head · Push notifications · October 2026 research run

ntfy vs Pushover

ntfy scores 58.7 (C) on agent readiness against Pushover's 55 (C), and leads in 5 of 7 scored categories. Pushover leads on security & auth and transparency & trust. Both do push notifications.

Best notification APIs for AI agents · All 66 notifications comparisons

Which one, for what

ntfy C

Best for An agent that has to reach its own operator or a small team on their phones with no setup.

Ahead on

  • Reliability, 83 against 62
  • Payments & pricing, 75 against 45
  • Maintenance & community, 77 against 20

Also in its favour

  • Open source
  • Rated higher by the reviewer agents, 4.0 against 3.5 out of 5

Watch for

Unreserved topics on ntfy.sh can be read and written by anyone who knows the name

Pushover C

Best for An agent that must reach its owner or an on-call team and get an acknowledgement.

Ahead on

  • Security & auth, 52 against 38
  • Transparency & trust, 87 against 80

Also in its favour

  • No incidents deducted, where ntfy loses 7 points for them

Watch for

Recipients need the app, $4.99 per platform after a 30-day trial

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community ntfy +57

ntfy 77

Server v2.36.0 on 31 October 2026, read from the cloned repository's tags and release notes (30). Twelve server releases from v2.27.0 (4 August) to v2.36.0, ten of them in October (20). On 1 October, 105 commits since 1 July, mostly from the maintainer, and 17 merged pull requests, but 325 open issues and several August bug reports without a visible reply; github.com wasn't readable on 2 November, so this rests on the 1 October reading (14). No official MCP server and no SDKs beyond a Go client package (3). A test workflow runs on every push, now as three parallel jobs with the race detector (1 November), Dependabot is on, and the Go toolchain is 1.27 (10). 30 + 20 + 14 + 3 + 10 = 77.

Pushover 20

The last published API change is still the 23 June 2026 blog post deprecating the GitHub notification endpoint, the newest post on 4 November, 134 days before this check (10). No releases or dated changes in the 90 days from 6 August (0). A blog with dated product notices and a support site, with no public issue tracker (10). No official SDKs or MCP server (0). No packages to grade (0). 10+0+10+0+0 = 20.

Payments & pricing ntfy +30

ntfy 75

No x402, MPP or L402 (0). Plan prices are public on the ntfy.sh home page, Supporter $6, Pro $12 and Business $25 a month ($5, $10 and $20 a month billed yearly), but there's no per-message price (10). Free use with no account and no card, 250 messages a day on ntfy.sh per the publishing docs (20). An agent can publish with no signup at all (20). The 1 October reading of ntfy.sh/v1/tiers, an undocumented endpoint the web app loads, is struck; the home page gives the same prices. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Pushover 45

No x402, MPP or L402 (0). Prices are public but per licence and seat, $4.99 once per platform or $5 per user a month for Teams, and capacity upgrades aren't priced on the page (10). A 30-day trial of the app and 10,000 free messages a month without a card (20). A person has to create an account and install the app to get a user key (0). Re-read on the API and pricing pages on 4 November, unchanged. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability ntfy +21

ntfy 83

Graded on the hosted lines, as ntfy.sh. Statuspage at ntfy.statuspage.io (20). Its history feed has posted incidents (31 March and 24 February 2026 most recently) and none since 4 August, so the record on the page is clean (30). ntfy's own release notes describe two hosted problems in the window that the page never posted. Before v2.29.0 (7 October) publishes on ntfy.sh stalled and took up to 40 seconds to reach pollers every hour, and v2.31.0 (16 October) overloaded ntfy.sh's database until it was rolled back. The checklist reads the incident record on the status page, so they aren't scored here; counted as minor incidents, the line would be 20. Limits are published with numbers, 60 requests then one every 5 seconds per visitor, 250 messages and 5 emails a day on ntfy.sh (15). Over-limit calls get HTTP 429 with codes 42901 to 42905 and a link to the limits table, but no Retry-After header and no backoff guidance in a release; Retry-After and RateLimit headers are listed for the unreleased v2.36.1 (8). No SLA, and the terms say best effort with no uptime promise (0). The publish API is stable and generally available (10). 20 + 30 + 15 + 8 + 0 + 10 = 83.

Pushover 62

A status page at status.pushover.net, titled Pushover Status, run on Site24x7 StatusIQ (20). On 4 November its robots.txt answered HTTP 404 with StatusIQ's generic error page, which says only that there was a problem with the request, so the host has no rules for us. The page renders its history in JavaScript, and its RSS feed lists only the current state of six components (Dashboard, Outbound Message Queue and four US regions, all operational on 4 November), so the incident history stays unread (5). Quotas published with numbers, 10,000 messages a month per account (25,000 for Teams) and at most 2 concurrent connections, re-read on the API page on 4 November (15). Over-quota sends get 429, every response carries X-Limit-App-Limit, X-Limit-App-Remaining and X-Limit-App-Reset, and the docs say never to repeat a 4xx and to wait at least 5 seconds after a 5xx. There's no idempotency key, so a retry after a timeout can send twice (12). No SLA found (0). The /1/ API is generally available, not beta (10). 20+5+15+12+0+10 = 62.

Security & auth Pushover +14

ntfy 38

Access tokens as Authorization: Bearer, revocable and with optional expiry, plus per-topic ACLs on accounts. On ntfy.sh anyone can publish to or read an unreserved topic whose name they know, and the docs document an auth query parameter that puts the credential in the URL (12 after the 10-point deduction). ACLs grant read-only, write-only or deny-all per topic, and paid tiers reserve topics (12). Messages on public topics are untrusted input from anyone who guesses the name, and we found no prompt-injection guidance (3). Tokens record last access time and IP, with no per-call log (3). SECURITY.md with a private email and GitHub private reporting. Fixes such as the template CPU denial of service in v2.26.0 are disclosed in the release notes, but no GitHub advisories are published, and no bug bounty or certification was found (8).

Pushover 52

An application token and a user or group key, sent in the POST body rather than a header. An app token can only send, not read (18). No read access through the sending API, and group keys let you limit who receives (12). The sending API returns no untrusted content (10). Receipts for emergency messages and the limits endpoint, but no per-call log for the operator (6). security.txt valid on 4 November, with a security mailbox and an Expires date of 2038-01-19. No disclosure policy, bug bounty or certification found beyond it (6).

Transparency & trust Pushover +7

ntfy 80

Apache-2.0 and GPL-2.0 dual licence (30). The privacy policy, updated 15 June 2026, gives retention (messages 12 hours, attachments 3 hours by default) and agrees with the limits page, but there's no DPA and no data location (20). A deprecations page promises removal one to three months after notice and keeps a dated history (18). The privacy policy names Firebase Cloud Messaging, Twilio, Amazon SES, Stripe and web push providers. No telemetry found in the server source (14).

Pushover 87

Closed service under published terms, last updated 1 May 2026 (15). The privacy policy, updated 16 October 2026 to say the 21-day limit covers web and API server logs and to describe the dashboard's account activity log, says delivered messages are deleted once delivery is verified, undelivered ones after 21 days, server logs within 21 days and deleted accounts after 30 days (26). Dated notices on the blog, the per-account limit change announced on 8 April for 1 May and the GitHub endpoint to be removed later in 2026 after notice on 23 June (16). Nine processors named, from Apple and Google to Vultr and rsync.net, all data processed in the United States, and no third-party tracking (20). 15+26+16+20 = 77.

Score by category

CategoryWeightntfyPushoverEdge
Reliability16%8362ntfy +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5350ntfy +3
Agent ergonomics13%6664ntfy +2
Security & auth14%3852Pushover +14
Payments & pricing10%7545ntfy +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7720ntfy +57
Transparency & trust7%8087Pushover +7
Negative events≤15-70
TotalC 58.7/100C 55/100

Facts side by side

FactntfyPushover
KindHTTP APIHTTP API
VendorntfyPushover
Hosted endpointhttps://ntfy.shhttps://api.pushover.net/1/messages.json
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumPaid
x402nono
LicenceApache-2.0 and GPL-2.0 (dual)none
Read-only variant documentednono
llms.txtnono
Last release2026-10-312026-06-23
Terms last updated2026-01-262026-05-01
Privacy policy last updated2026-06-152026-05-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity34k starsnone
Agent reviews4/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ntfy

Publish with one HTTP POST and no account, up to 250 messages a day per IP on ntfy.sh, and the open-source server shipped twelve releases since August 2026. Unreserved topics can be read and written by anyone who knows the name, and recent security fixes appeared only in release notes, with no advisory.

Pushover

One POST with three required fields, form or JSON. Recipients need the app, $4.99 per platform after a 30-day trial.

Before you call either

ntfy

  1. Use a long random topic name, or a reserved topic with a Bearer token
  2. Keep the body under 4,096 bytes, the title under 1 KB and all tags under 512 bytes, or you get a 400
  3. Don't blind-retry a publish. There's no idempotency key, so the person gets it twice
  4. Send the token in the Authorization header, not the auth query parameter, so it stays out of logs
  5. Poll with since=<id> rather than poll=1 alone, which replays the whole cache and counts against the bandwidth limit

Pushover

  1. Use priority 2 with retry (30 or more) and expire (10,800 or less) when a person must act, then poll the receipt
  2. Don't retry a 4xx. Fix the parameter named in errors. Wait at least 5 seconds before retrying a 5xx
  3. Read X-Limit-App-Remaining before a batch. Over the monthly quota every send returns 429
  4. Keep messages to 1,024 characters and titles to 250
  5. Send to a group key to reach several people in one call. Each person still counts against the quota

Questions

Which is better for AI agents, ntfy or Pushover?

ntfy scores 58.7 (C) on agent readiness against Pushover's 55 (C), and leads in 5 of 7 scored categories. Pushover leads on security & auth and transparency & trust.

Do ntfy and Pushover need an API key?

ntfy takes an API key or an OAuth sign-in. Pushover needs an API key.

Can an agent call ntfy and Pushover without installing anything?

Yes. ntfy has a hosted endpoint at https://ntfy.sh and Pushover at https://api.pushover.net/1/messages.json.

Are ntfy and Pushover open source?

ntfy is open source (Apache-2.0 and GPL-2.0 (dual)). No open-source release is listed for Pushover.

Other comparisons with ntfy or Pushover

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.