Documentation

Ntfyx vs ntfy, Bark, Pushover and Gotify: choose by workflow

Compare the same backup alert and human confirmation workflow in Ntfyx, ntfy, Bark, Pushover and Gotify, with platforms, prices, retention and official sources checked 28 October 2026.

Updated 29 October 2026

The short answer

Choose Ntfyx when you want incoming task messages and an answer that stays with its original question, in a hosted app with optional phone-only notification subscriptions. Evaluate ntfy for general publish/subscribe and actions, Bark for custom iPhone push, Pushover for API alerts and acknowledgment receipts, or Gotify for a server you operate with Web/Android receivers.

Send the same backup alert with Ntfyx or ntfy

Use the harmless message “Backup test failed (exit 1)” in either setup below. Both paths work without pairing a computer. Ntfyx HTTPS Push uses a private sending URL prepared on the phone; ntfy can publish anonymously to a topic you choose. These examples send a test message, not a backup or a retry.

On a small screen, swipe the table to read every column.

Step	Ntfyx HTTPS Push	ntfy
Prepare the receiver	Open HTTPS Push in the phone app, wait for it to be ready, and copy the complete sending link.	In the ntfy phone app, subscribe to a long, unique topic on ntfy.sh. The same topic name goes into the sending URL.
Configure the script	Set NTFYX_PUSH_URL privately to the copied link. It grants sending only; anyone who gets it can send.	Set NTFY_TOPIC to the chosen topic. An unreserved public topic permits anyone with its name to read and send.
Observe the result	Check MyNotify in the app, then check the phone alert separately. The service reads HTTPS input before encrypting delivery.	Check the subscribed topic and phone alert separately. Use access controls or your own server when anonymous topic access does not fit.

# Run either command after configuring its variable.
# Ntfyx: use the complete HTTPS Push link copied from your phone.
curl --fail-with-body --silent --show-error --max-time 30 \
  -H "Content-Type: text/plain; charset=utf-8" \
  --data-binary "Backup test failed (exit 1)" "${NTFYX_PUSH_URL:?Set the private sending URL}"

# ntfy: use the same topic you subscribed to in its phone app.
curl --fail-with-body --silent --show-error --max-time 30 \
  --data-binary "Backup test failed (exit 1)" "https://ntfy.sh/${NTFY_TOPIC:?Set your topic}"

Public Topics are a separate Ntfyx option

With an existing public Topic ID or link, CLI 0.6.0 can send and read without pairing, a key or a Ntfyx account. The phone follows that existing Topic; following does not create one. Public content is readable by the service and anyone with the link, and cannot carry answers, approvals or Call reminders.

Each accepted public message counts against the Topic owner’s daily message allowance; following uses the follower’s subscription slot.

ntfyx public info --topic TOPIC_ID --json
ntfyx public send "Backup test failed (exit 1)" --topic TOPIC_ID --accept-public-terms --json
ntfyx public read --topic TOPIC_ID --limit 5 --json

Choose the interaction you need

A notification action, an acknowledgment receipt and an answer tied to a question solve different parts of a workflow. MCP integration and encryption can be useful, but neither word alone describes the full user experience.

On a small screen, swipe the table to read every column.

Tool	Documented interaction and context
Ntfyx	Confirm, choose an option or send a quoted text reply. Replies stay with the original question; related task updates share a Session.
ntfy	Up to three notification actions can open links, send HTTP requests, copy text or use Android broadcasts. Client support varies. Define and test any additional question/reply contract you need.
Bark	The official API supports custom push and grouping; its tutorial also documents MCP integration. For an original-question answer and task continuation workflow, verify or implement the response contract separately.
Pushover	Emergency-priority notifications have acknowledgment receipts and callbacks. A receipt is a delivery/acknowledgment workflow; your integration must define what it authorizes.
Gotify	A built-in /mcp endpoint exposes send_message with a send-only application token. Message extras support click URLs and Android intents. Sending an input-needed alert does not itself supply an authenticated answer to that input.

Ask a person before retrying the backup

Start with the same question: “Review the backup failure and allow one retry?” A button, acknowledgment and signed answer can all be useful. The integration must define exactly which action may follow.

On a small screen, swipe the table to read every column.

Tool	What the person does	What the sender must check
ntfy	Tap a notification action that opens a review page or sends an HTTP request to your endpoint.	Your endpoint supplies authentication, binds the request to this backup attempt, and rejects expired or repeated actions. Check action support on the chosen client.
Pushover	Acknowledge an emergency-priority notification.	Inspect its receipt or callback. Define whether that acknowledgment means “seen” or permission to retry; the receipt alone does not define the business action.
Ntfyx protected Topic	Allow or deny the original question on an authorized receiver.	Synchronous ask verifies the signed answer, original request and deadline, then claims it once. Only the requested, verified Allow permits the agreed retry; report the backup result separately.

ntfyx ask "Review the backup failure and allow one retry?" --allow-deny --wait 5m --json

Hosting, receiver and privacy choices

Choose the receiver platforms first, then who operates the server and which encryption mode is enabled. TLS, self-hosting and end-to-end content encryption answer different questions. Other products also document encrypted content; Ntfyx does not claim encryption as an exclusive feature.

On a small screen, swipe the table to read every column.

Tool	Deployment and receivers	Privacy scope to check
Ntfyx	Hosted service. iPhone, Android and Web; protected Web Inbox access needs phone authorization. The companion CLI supports macOS, Linux and Windows. No supported self-host package.	Protected Topic CLI and agent message titles, bodies, options and replies are end-to-end encrypted on your devices. Public Topic names and messages are readable by the service and anyone with the Topic ID or link. The explicit fixed monitor-access and webhook-management questions and their signed phone answers are disclosed to the service for verification. HTTPS push and webhook requests are readable by the service before encrypted delivery. Optional provider verification secrets are encrypted and stored by the service, then used in plaintext to verify the raw webhook body; they are hosted secrets, not hidden from the service. My Monitor reads the monitored address, rule and response; a public publisher knows the content it publishes. The relay routes ciphertext and processes operational metadata such as identifiers, time, size and push tokens. Do not put secrets in monitored URLs or request examples. Independent security review is not complete.
ntfy	Hosted ntfy.sh or your own server; Android, iOS and Web clients.	The reviewed privacy documentation explains transport encryption and message handling. Self-hosting changes who operates the server; a native E2EE mode was not established by the documents reviewed here.
Bark	iPhone app with an open-source, self-hostable server.	Optional encrypted push is documented. Check how your sender and iPhone share the encryption key; encrypted content is not unique to Ntfyx.
Pushover	Hosted service with Android, iOS and desktop browser receivers.	The API documents optional sender-to-device E2EE with encrypted=1 for iOS/Android. Check mode and client requirements rather than assuming every notification uses it.
Gotify	Open-source server and Web UI, with an Android client.	Self-hosting puts the server under your control. Evaluate the chosen transport, server access and client encryption mode; self-hosting alone is not proof of E2EE.

Prices, retention and limits

Compare the allowance period and who operates storage, not just the plan name. The figures below were checked on 28 October 2026; hosted checkout and local app-store prices remain authoritative. Self-hosting adds your own hosting and maintenance costs. Device history is separate from server retention.

On a small screen, swipe the table to read every column.

Tool	Price and sending allowance	Server retention and limits
Ntfyx	Free: 100 messages/UTC day. Plus: US reference $1.99/month, 1,000/day. Pro: $9.90/month, 20,000/day. Call and answer requests share those totals; monitor and subscription slots also apply.	Ordinary public messages and protected relay ciphertext: at most 24 hours, within storage capacity. Pending questions last to their deadline; terminal request/answer data lasts another 24 hours. This is not unlimited history.
ntfy.sh	Anonymous use is free with 250 messages/day on ntfy.sh. Hosted paid plans increase limits; Supporter lists $6/month with monthly billing, or $5/month equivalent with annual billing.	Default message cache: 12 hours. Default attachment expiry: 3 hours. Published free-host limits include 4,096-byte messages and 2 MB attachments; self-host settings and paid tiers can differ.
Bark	The official project describes the app as free. A self-hosted server has your own operating costs.	Check the selected server and iPhone history settings. The linked overview and tutorials do not establish a uniform hosted quota or retention promise.
Pushover	Individual license: US $4.99 once per receiving platform, after a 30-day trial. The account shares 10,000 API messages/month across its applications; higher capacity and Teams are separate.	Deleted from the server after delivery is verified; unverified messages expire after 21 days. API message body limit: 1,024 UTF-8 characters. Device copies have their own history.
Gotify	Open-source software you operate; budget for server, storage and maintenance instead of a hosted plan.	Storage and access settings belong to your deployment. Review its database cleanup and backup policy; no shared hosted retention or message allowance is assumed here.

What the Ntfyx workflow includes

In a protected Topic, allow or deny one request, choose an offered option or type a text answer. Select Reply on the question to open a quoted composer. Your answer stays below that question, and the sending computer verifies the signed reply. Sending a reply does not prove an external action has completed.

A Topic groups messages from sources you authorize. Use the same session ID inside the same Topic to keep one task’s updates and replies in a Session conversation. Without a session ID, each new message starts a separate conversation. Grouping does not grant access to other Topics or export the agent’s whole transcript.

Your tool sends an update or a question into the authorized Topic.
Open the task conversation and answer the original question.
The sender receives and verifies the answer, then continues its own task.
A later message can report the result in that same conversation.

Free start and service scope

No. Open Discover in the iPhone or Android app, review a public notification source and confirm its subscription. No computer, CLI, pairing scan or Ntfyx account is needed. Receive future editions in its Topic; pause or unsubscribe from the phone. Each source lists its coverage and schedule. Private agent messages are not used to generate these updates.

Free includes 100 messages per UTC day, including up to 10 Call reminders and 10 answer requests, one monitor and one subscription. Notification-source subscriptions and public follows share the subscription allowance. Topic count is not a paid entitlement. Public Topics support ordinary and rich messages; protected Topics also support verified answers and Call reminders.

When to choose another approach

If operating your own notification server is a requirement, start with the self-hostable tools above. If you only need a completion alert, a simple publish API may be enough. If you need a general conversation with contacts, full remote desktop access or arbitrary terminal-input forwarding, that is outside Ntfyx’s documented scope.

Android push requires Google Play services; agent approval support has specific host and platform requirements.

Is Ntfyx the same product as ntfy (ntfy.sh)?

No. Ntfyx (ntfyx.me) and ntfy (ntfy.sh) are separate products with no affiliation. Ntfyx brings command and script notifications, agent questions and phone replies into one Inbox. ntfy is an HTTP publish/subscribe notification service with hosted and self-hosted options.

What makes Ntfyx different from a push notification tool?

Ntfyx combines received messages, answers attached to the original question and task conversations. You can also subscribe to selected notification sources directly on the phone. Compare the complete workflow you need: other tools support useful actions, receipts, encryption or MCP too.

Do I need a computer for notification-source subscriptions?

Are MCP integration or encrypted notifications unique to Ntfyx?

No. Gotify and Bark document MCP integration. Bark documents encrypted push, and Pushover documents optional end-to-end encryption for iOS/Android. Ntfyx’s proposed fit is the combination of original-question replies, task context, phone authorization and optional source subscriptions.

Does a button click or sent reply mean that the task finished?

No. Receiving a notification, acknowledging it, authorizing a request and completing an external action are separate events. Ntfyx lets the sender verify an answer tied to the request; your tool still has to execute the action and report the result.

When is Ntfyx not the right fit?

If supported self-hosting is required, evaluate ntfy, Bark or Gotify. Ntfyx is not a general contact messenger or a way to forward arbitrary terminal input. Its CLI supports macOS, Linux and Windows; native agent approval behavior has separate host and platform requirements.

Official sources and verification date

Sources below were checked on 28 October 2026. Features can change, and a documented API capability may require client configuration or custom integration. For Ntfyx, the linked product guides describe the supported workflow and its limits; this page makes no claim of faster delivery, unique encryption or independent certification.

Compare ways to use coding agents from your phone

Compare full-session access, completion notifications, permission decisions and answers, with official sources, encryption scope, account requirements and starting prices.

Claude Code and Codex on your phone

Choose by the workflow you need

For Ntfyx, compare five separate needs: task completion, a signed answer attached to its question, a send-only HTTP event, an optional call-style reminder, and an hourly status/text/JSON check. Other products may also support replies or actions; evaluate their current documentation against your own requirements.