Push alerts from any service that sends webhooks.
Simplepush relaunched in September 2026 as a two-way tool: send a task to a phone, collect the answer, and let an AI agent search what came back. It has a generous free tier, five priority levels and opt-in end-to-end encryption. What it does not do is take webhooks from other services. Pocket Alert is built for that side of alerting: a webhook URL per source with field mapping and a log of every call, scheduled delivery, action buttons that call an endpoint, and a history you can open in the app and the dashboard.
Where Simplepush is not built for alerts
Its new focus is tasks for people in the field. Alerts from your own infrastructure need a few different things.
No inbound webhooks
GitHub, Grafana or Stripe cannot post their own JSON to Simplepush. Every source has to call its API with its headers, so a script sits in between.
Alerts do not stay
A notification leaves no record on the phone once dismissed. History is read through the CLI or an agent, needs a subscription, and is pruned after three months.
No scheduling
There is no scheduled or delayed delivery. Sending something at 9am tomorrow means your own cron or an agent’s scheduler.
Buttons answer, they do not act
Buttons return a key to the sender, or open one link. None calls an HTTP endpoint or copies a value on its own.
Pocket Alert vs Simplepush, feature by feature
Both send from one HTTP request to iPhone and Android. The difference is what happens before the request and after the tap.
| Feature | Pocket Alert | Simplepush |
|---|---|---|
| Where you use it | ||
| iOS app | iOS 15.1 and later | |
| Android app | Android 7 and later | |
| Web dashboard | Devices, keys, apps, webhooks | Not documented |
| Chrome extension | Send a link or note to your phone | |
| Command-line tool | Official binary for Linux, macOS, Windows | sp, open source |
| MCP server for AI agents | 10 tools | Hosted, 14 tools |
| Sending alerts | ||
| Send via HTTP API | Header-based or JSON | |
| Inbound webhook URL per source | One URL per service | |
| Payload mapping into the message | %field.path% into title, body and buttons | |
| Scheduled delivery | Up to 30 days, listable and cancellable | Task deadlines only |
| Priority levels | Five, silent to critical | Five, 1–5 |
| Critical alerts that override Do Not Disturb | On paid plans | Priority 5 on iOS and Android |
| Action buttons on the notification | Up to 3: open, HTTP request, copy | Answer buttons or one link, no HTTP or copy |
| Attachments | Images | Photos, audio and files via SDK or CLI |
| Grouping by source | Applications, filtered in the app | Topics |
| Email delivery | ||
| SMS or phone-call delivery | ||
| Records and debugging | ||
| Message history | Account-wide, synced to app and web | Through the CLI or MCP, on paid plans |
| Webhook call log | Headers, payload, rendered message, result | |
| History retention | Messages until you delete them; webhook calls 7–365 days by plan | Pruned after 3 months |
| Delivery statistics | Per application and per device | |
| Account and data | ||
| Content encryption | At rest with a per-account key, secrets redacted | Opt-in end-to-end |
| Two-factor authentication | TOTP with recovery codes | Not documented |
| Open source or self-hosted | CLI and SDKs are open source | |
Simplepush relaunched as a new product on 9 September 2026. Data from simplepu.sh (guide, changelog, pricing, privacy) and its App Store and Google Play listings, checked October 2026.
What you’ll pay
| Pocket Alert | Simplepush | |
|---|---|---|
| Free plan | 50 messages a day, no card | 2,500 requests a day, end-to-end encryption included |
| Entry paid plan | $6/month — 1,000 messages a day, 5 webhooks | Solo, $6/month — 10,000 requests a day |
| Highest tier | $25/month — unlimited messages, 365-day history | Team, $12 per seat / month |
Pocket Alert pricing as of October 2026. Simplepush figures from simplepu.sh. See full pricing.
Coming from Simplepush
Install and get a key
Install the app on your iPhone or Android phone, sign in, and copy your API key from the dashboard.
Swap the endpoint
Move Title and Content from headers into a JSON body as title and message. Priority 4 becomes high, 5 becomes critical.
Point services at webhooks
For services you were bridging with a script, create a webhook and map their JSON with %field.path%.
Keep tasks where they work
If you collect answers from people in the field, that is where Simplepush is strong. Move the alerts, keep the tasks.
curl -X POST https://api.simplepu.sh/v1/notifications \
-H 'API-Token: YOUR_API_TOKEN' \
-H 'Title: Deploy finished' \
-H 'Content: main is live' \
-H 'Priority: 4'curl https://api.pocketalert.app/v1/messages \
-H 'Token: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"title": "Deploy finished",
"message": "main is live",
"level": "high"
}'Questions, answered
Since September 2026 Simplepush is built around two-way tasks: you send a question to a phone, get an answer back, and an AI agent can search everything that came in. Pocket Alert is built around one-way alerts from your systems: a webhook URL per source with field mapping, a log of every call, scheduled delivery, action buttons that call an endpoint or copy a value, and a history in the app and the web dashboard.
Simplepush, by a wide margin: 2,500 requests a day, against 50 messages a day on Pocket Alert’s free plan. Paid plans start at $6 a month on both, with 10,000 requests a day on Simplepush Solo and 1,000 messages a day on Pocket Alert, which also adds devices, webhooks and scheduling.
Simplepush offers opt-in end-to-end encryption for personal accounts and whole organizations, so its servers cannot read the content. Pocket Alert does not do end-to-end: it encrypts content at rest with a key per account, redacts authorization headers before storing webhook payloads, and offers TOTP two-factor on the account. If the server must never read a message, Simplepush covers it and Pocket Alert does not.
Not according to its documentation. Every request uses Simplepush’s own API with an API-Token header, so a service that only sends its own webhook JSON needs a script in between. A Pocket Alert webhook takes the raw payload, maps fields into the title, body and buttons with %field.path%, and records each call with its headers, payload and result.
On Simplepush a notification leaves no record on the phone once it is dismissed. History lives on the server, is read through the CLI or an AI agent, needs a subscription on personal accounts, and is pruned after three months. Pocket Alert keeps message history in the app and the dashboard until you delete it, and logs webhook calls for 7 to 365 days depending on plan.
Alerts in from anywhere, on record.
Point a service at a webhook URL, map the fields, and keep every alert in a history you can open anywhere.