# Pocket Alert vs Pushover

> Pushover alternative for developers: a full webhook call log, scheduled delivery up to 30 days, action buttons and account-wide message history. Free tier, iOS and Android apps.

<!-- source: https://pocketalert.app/alternatives/pushover -->

Pushover has been delivering push reliably for over a decade, its API is as simple as they come, and since 2026 it receives webhooks too. Pocket Alert covers the same ground and adds what sits around it: a log of every webhook call with its payload and rendered result, scheduled delivery, action buttons on the notification, and history that lives on the account instead of on each device.

## What Pushover does not cover

Pushover does one job well. These are the jobs it leaves to you.

- **No action buttons** — A notification carries one supplementary URL. There is no button to call a restart endpoint or copy an ID from the lock screen.
- **Nothing to debug with** — Webhooks show only the last payload received. When an alert never arrives, there is no record of earlier calls, their headers, or why one failed.
- **History is per device** — Messages live on each device separately and are not viewable on the website, so history depends on the phone in your hand.
- **No scheduling** — A message sends the moment you call the API. Delivering it at 9am tomorrow means running your own cron.

## Pocket Alert vs Pushover, feature by feature

Same delivery job, different amount of plumbing left over.

### Where you use it

- **iOS app** — Pocket Alert: Yes; Pushover: Yes
- **Android app** — Pocket Alert: Yes; Pushover: Yes
- **Web dashboard** — Pocket Alert: Yes (Devices, keys, apps, webhooks); Pushover: Yes (Account, apps, groups; plus a desktop client)
- **Chrome extension** — Pocket Alert: Yes (Send a link or note to your phone); Pushover: No
- **Command-line tool** — Pocket Alert: Yes (Official binary for Linux, macOS, Windows); Pushover: No (Community scripts only)
- **MCP server for AI agents** — Pocket Alert: Yes (10 tools); Pushover: No

### Sending alerts

- **Send via HTTP API** — Pocket Alert: Yes; Pushover: Yes
- **Inbound webhook URL per source** — Pocket Alert: Yes (One URL per service); Pushover: Yes (Webhook receivers since February 2026)
- **Payload mapping into the message** — Pocket Alert: Yes (%field.path% into title, body and buttons); Pushover: Yes ({{field}} selectors for title, body, URL, image)
- **Scheduled delivery** — Pocket Alert: Yes (Up to 30 days, listable and cancellable); Pushover: No
- **Priority levels** — Pocket Alert: Yes (Five, silent to critical); Pushover: Yes (Five, -2…2, emergency retries until acknowledged)
- **Critical alerts that override Do Not Disturb** — Pocket Alert: Yes (On paid plans); Pushover: Yes (iOS Critical Alerts, Android DND override)
- **Action buttons on the notification** — Pocket Alert: Yes (Up to 3: open, HTTP request, copy); Pushover: Partly (One supplementary URL, no buttons)
- **Attachments** — Pocket Alert: Yes (Images); Pushover: Yes (Images up to 5 MB)
- **Grouping by source** — Pocket Alert: Yes (Applications, filtered in the app); Pushover: Yes (Applications and delivery groups)
- **Email delivery** — Pocket Alert: No; Pushover: Yes (E-mail gateway to your devices)
- **SMS or phone-call delivery** — Pocket Alert: No; Pushover: No

### Records and debugging

- **Message history** — Pocket Alert: Yes (Account-wide, synced to app and web); Pushover: Partly (Per device, not on the website)
- **Webhook call log** — Pocket Alert: Yes (Headers, payload, rendered message, result); Pushover: Partly (Last payload only)
- **History retention** — Pocket Alert: Yes (Messages until you delete them; webhook calls 7–365 days by plan); Pushover: Partly (Whatever the device kept)
- **Delivery statistics** — Pocket Alert: Yes (Per application and per device); Pushover: Partly (Monthly message counter)

### Account and data

- **Content encryption** — Pocket Alert: Yes (At rest with a per-account key, secrets redacted); Pushover: Partly (In transit; storage not documented)
- **Two-factor authentication** — Pocket Alert: Yes (TOTP with recovery codes); Pushover: Yes
- **Open source or self-hosted** — Pocket Alert: No; Pushover: No

Pushover data from pushover.net, its API documentation and blog, checked October 2026.

## Pricing

- **Free plan** — Pocket Alert: 50 messages a day, no card; Pushover: 30-day trial, then a purchase per platform
- **Entry paid plan** — Pocket Alert: $6/month — 1,000 messages a day, 5 webhooks; Pushover: $4.99 once per platform, after a 30-day trial
- **Highest tier** — Pocket Alert: $25/month — unlimited messages, 365-day history; Pushover: Pushover for Teams, $5 per user / month

Pocket Alert pricing as of October 2026. Pushover figures from pushover.net/pricing.

## Coming from Pushover

1. **Install and get a key** — Install the app, sign in, and copy your API key from the dashboard.
2. **Swap the endpoint** — Point your existing script at the Pocket Alert endpoint. Same POST, same title and message fields.
3. **Replace the bridges** — For each Pushover webhook or third-party bridge, create a Pocket Alert webhook and map the payload with %field.path%.
4. **Set the levels** — Set a default level per webhook so routine events stay quiet and the ones that matter break through.

### Before: Pushover

```bash
curl https://api.pushover.net/1/messages.json \
  --form-string 'token=YOUR_APP_TOKEN' \
  --form-string 'user=YOUR_USER_KEY' \
  --form-string 'title=Deploy finished' \
  --form-string 'message=main is live' \
  --form-string 'priority=1'
```

### After: Pocket Alert

```bash
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"
  }'
```

## FAQ

### What can Pocket Alert do that Pushover cannot?

Since February 2026 Pushover has webhook receivers too, with selectors that pull JSON fields into the title, body, URL and image. What Pocket Alert adds around them: a log of every incoming call with its headers, payload and rendered message (Pushover shows the last payload), scheduled delivery up to 30 days out, up to three action buttons on the notification, and history kept on the account instead of on each device.

### Where does message history live?

Pushover stores messages on each device separately, and they are not viewable from the website. Pocket Alert keeps message history on the account, so it is the same list on your phone and in the dashboard, with delivery statistics next to it.

### Can I schedule a message for later?

Add `send_at` with an exact time or `delay` with a duration to any message. It is stored encrypted until the delivery time, up to 30 days out, and you can list or cancel anything still pending. Pushover has no scheduling — messages send when you make the request.

### How does the pricing compare?

Pushover is $4.99 once per platform after a 30-day trial, with a 10,000 messages per month allowance; Pushover for Teams is $5 per user per month. Pocket Alert is a subscription: free for 50 messages a day, $6/mo for 1,000 a day, $25/mo for unlimited. For one person sending a handful of alerts, Pushover costs less over time. The subscription buys the call log, the history and the scheduling.