Agent Notifier vs ntfy vs Pushover: the difference is the round trip

If all you need is a phone buzz when a script finishes, Pushover and ntfy are excellent and you should probably use one of them. This post is about the two things they were never built to do: let an agent ask you something and carry on once you answer, and put the actual work - the diagram, the diff, the screenshot, the narrated summary - on your phone instead of a 40-character teaser.

The short answer

These three products look almost identical on a feature grid and are actually solving different problems.

Everything below is sourced from vendor documentation, verified on 31 July 2026, and linked at the bottom. Where a competitor is better, we say so.

The question that actually separates them

Run a coding agent for an afternoon and you will hit this moment. It has written the migration and needs to know whether to drop the column. It has three plausible refactors and needs you to pick. It is about to run something destructive and wants a yes.

A notification tells you that happened. It does not help you answer. With a traditional push service the loop is: buzz, walk to the laptop, read the terminal, type, resume. The agent sits idle the whole time, and the notification saved you nothing except the discovery that it was waiting.

What you actually want is for the agent to block, for the question to arrive on your phone with its choices, and for your answer to go straight back to the process that was waiting. That is a round trip, not a notification - and it is the axis on which these three products genuinely differ.

What it looks like when it is built in

Agent Notifier ships hooks for Claude Code and Copilot CLI, and installing them is one command. After that, when the agent asks a question the hook blocks it, the question arrives on your phone with its answer choices, and whatever you pick is returned to the agent as the tool result. The agent keeps going. You never opened the laptop.

curl -fsSL https://notifier.aicrew.in/install.sh | sh

The same channel carries permission approvals, and wrapping any interactive command relays its device codes and passphrase prompts to your phone too. If the hook cannot reach us it emits no decision at all and your agent falls back to its normal local prompt - a dead phone must never be able to wedge your agent.

The other half: what actually arrives

The second thing a generic notification service cannot do is show you the work. Agents do not produce one-line statuses. They produce diffs, architecture diagrams, test output, screenshots, generated files, and long written summaries. Pushover gives you 1,024 characters and one image. ntfy gives you plain text and an attachment.

Agent Notifier renders the substance in the notification and in the feed, so triage from a phone is real triage rather than a prompt to go and look somewhere else.

The one people do not expect: send text as audio

This is the feature that changes how people actually use the product, and neither competitor has anything like it.

Add --as-audio and the server narrates the message into speech, attaches it, and delivers it as playable audio. Point it at a Markdown or text file and it will narrate the whole document. You pick the voice and the speed.

notify.py "Nightly report ready" --as-audio \
  --file-path ./reports/nightly.md --voice af_bella --speed 1.1

Playback keeps running when the app is backgrounded or the phone is locked, with proper lock-screen controls. So the overnight agent run becomes something you listen to on the walk to the coffee shop rather than a wall of text you promise yourself you will read later. Long scripts are chunked automatically rather than failing.

ntfy can place a text-to-speech phone call on paid plans with a verified number, which is a genuinely useful escalation tool - but it is a call, not an attached recording you can scrub, pause, and replay. Pushover has no equivalent.

The boring parts that still matter

Who can publish to your topic

One row there deserves expanding. ntfy’s public instance is open by design: anyone who knows a topic name can read it and publish to it, and the docs are refreshingly candid that a topic name is obscurity, not authentication. For hobby alerts that is a reasonable trade. For an agent that receives approval decisions, a channel a stranger can guess and write to is the wrong shape entirely. Self-hosted ntfy fixes this properly with ACLs and deny-all defaults, and paid ntfy.sh tiers let you reserve topics.

Pricing, honestly

Pushover is the cheapest by a wide margin and it is not close. A one-time $4.99 per platform against $9.99 a month is roughly the difference between a coffee and a streaming subscription. If one-way alerts are all you need, paying us instead would be a bad trade. Self-hosted ntfy is cheaper still, at the price of running a server.

We charge a subscription because we run a stateful service. An approval waiting on your answer, media storage, and server-side narration are ongoing costs, not a one-time download.

Where the others are genuinely better

Pick ntfy if you want to own it

• Apache-2.0 and GPLv2, self-hostable from a binary, a package, or Docker. Your messages never leave your infrastructure.
• Excellent generic transport: HTTP, SSE, WebSockets, polling, cached retrieval, and multi-topic subscriptions. It composes into things we do not do.
• Publish from email, from curl, from anything. No SDK, no account required.
• One caveat worth knowing: for instant delivery from a self-hosted server, iOS needs an upstream relay, and the docs describe the iOS app as less mature than Android.

Pick Pushover if you want cheap and permanent

• $4.99 once per platform, then 10,000 messages a month, free, forever.
• Emergency priority that retries until a human acknowledges is a genuinely good design.
• Optional documented end-to-end encryption for iOS and Android message content.
• It has been reliable for over a decade. That is worth something real.

When Agent Notifier is the wrong choice

We would rather you pick correctly than churn in a month.

• You need to self-host. We are a hosted service. Use ntfy.
• You only send one-way alerts. Pushover does that well for a one-time fee.
• You need email-to-push or Android broadcast intents. ntfy has those; we do not.
• Your volume is enormous and uniform. Per-message pricing at scale may beat a flat subscription.

If any of this sounds like your week

The free tier is 100 notifications with every feature unlocked - approvals, rich media, Mermaid, narration, all of it. Enough to wire a real agent end to end and decide with evidence rather than a comparison table, including this one.

1. Install the harness: curl -fsSL https://notifier.aicrew.in/install.sh | sh
2. Run your agent until it asks you something.
3. Answer it from your phone, and watch the agent carry on.

Sources

All competitor claims were checked against vendor documentation on 31 July 2026. Pricing and limits change - if you find something out of date here, tell us and we will correct it.

• Pushover: pricing, message API and limits, receipts and acknowledgement, teams
• ntfy: hosted pricing, publishing and actions, access control, iOS instant notifications, source