Hosted APNs and FCM

Alerts that finally break through notification noise.

Reliable push notifications for on-call engineers. Delivered over APNs and FCM with native Alertmanager support.

Free forever with ten minutes to get running. No credit card required.

Get started free View docs

Handler critical alert on iPhone lock screen with Acknowledge over stacked infrastructure notifications

Channels

prod-alerts

grafana-oncall

cron-jobs

Delivered via APNs and FCM

142ms · acknowledged

even when the app is closed

Ready in 5 minutes after you create an account

How it works?

We built a universal way to open and close incidents, inspired by Alertmanager, but not tied to it. Any system that can POST a webhook can fire and resolve the same way. See the examples below.

1. Fire an Alert

alertmanager.yml

route:
  receiver: "handler"

receivers:
  - name: "handler"
    webhook_configs:
      - url: "https://api.gethandler.app/api/v1/alertmanager?token=YOUR_CHANNEL_TOKEN&user=YOUR_USER_KEY"
        send_resolved: true

2. Resolve the Alert

Inbox card: RESOLVED warning HighCPUUsage

alertmanager.yml

route:
  receiver: "handler"

receivers:
  - name: "handler"
    webhook_configs:
      - url: "https://api.gethandler.app/api/v1/alertmanager?token=YOUR_CHANNEL_TOKEN&user=YOUR_USER_KEY"
        send_resolved: true

1. Fire an Alert

curl

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=YOUR_CHANNEL_TOKEN&user=YOUR_USER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "fire",
    "title": "CPU above 90% for 5 minutes",
    "message": "Host app-01.example.net saturating CPU. Check runaway jobs.",
    "labels": {
      "alertname": "HighCPUUsage",
      "severity": "warning",
      "instance": "app-01.example.net:9100",
      "job": "node"
    }
  }'

2. Resolve the Alert

curl

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=YOUR_CHANNEL_TOKEN&user=YOUR_USER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "resolve",
    "title": "CPU above 90% for 5 minutes",
    "message": "Host app-01.example.net saturating CPU. Check runaway jobs.",
    "labels": {
      "alertname": "HighCPUUsage",
      "severity": "warning",
      "instance": "app-01.example.net:9100",
      "job": "node"
    }
  }'

Or Send a Message

Inbox card: Messenger notification Deploy finished

curl

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=YOUR_CHANNEL_TOKEN&user=YOUR_USER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "message",
    "title": "Deploy finished",
    "message": "Production deploy completed.",
    "priority": "high"
  }'

1. Fire an Alert

GitHub Actions

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=${{ secrets.HANDLER_TOKEN }}&user=${{ secrets.HANDLER_USER }}" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "fire",
    "title": "CPU above 90% for 5 minutes",
    "message": "Host app-01.example.net saturating CPU. Check runaway jobs.",
    "labels": {
      "alertname": "HighCPUUsage",
      "severity": "warning",
      "instance": "app-01.example.net:9100",
      "job": "node"
    }
  }'

2. Resolve the Alert

GitHub Actions

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=${{ secrets.HANDLER_TOKEN }}&user=${{ secrets.HANDLER_USER }}" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "resolve",
    "title": "CPU above 90% for 5 minutes",
    "message": "Host app-01.example.net saturating CPU. Check runaway jobs.",
    "labels": {
      "alertname": "HighCPUUsage",
      "severity": "warning",
      "instance": "app-01.example.net:9100",
      "job": "node"
    }
  }'

Or Send a Message

GitHub Actions

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=${{ secrets.HANDLER_TOKEN }}&user=${{ secrets.HANDLER_USER }}" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "message",
    "title": "Deploy finished",
    "message": "Production deploy completed.",
    "priority": "high"
  }'

1. Fire an Alert

Jenkinsfile

# Jenkinsfile, sh """ ... """
curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=${HANDLER_TOKEN}&user=${HANDLER_USER}" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "fire",
    "title": "CPU above 90% for 5 minutes",
    "message": "Host app-01.example.net saturating CPU. Check runaway jobs.",
    "labels": {
      "alertname": "HighCPUUsage",
      "severity": "warning",
      "instance": "app-01.example.net:9100",
      "job": "node"
    }
  }'

2. Resolve the Alert

Jenkinsfile

curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=${HANDLER_TOKEN}&user=${HANDLER_USER}" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "resolve",
    "title": "CPU above 90% for 5 minutes",
    "message": "Host app-01.example.net saturating CPU. Check runaway jobs.",
    "labels": {
      "alertname": "HighCPUUsage",
      "severity": "warning",
      "instance": "app-01.example.net:9100",
      "job": "node"
    }
  }'

Or Send a Message

Jenkinsfile

# Jenkinsfile, sh """ ... """
curl -sS -X POST \
  "https://api.gethandler.app/api/v1/universal?token=${HANDLER_TOKEN}&user=${HANDLER_USER}" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "message",
    "title": "Deploy finished",
    "message": "Production deploy completed.",
    "priority": "high"
  }'

Create a free channel Read the docs

Features

What you get

We do not like landings that hide what the product really looks like. Let the screens below show Handler in full, so you can decide if it is for you.

View all

Reliable Push Notifications

APNs and FCM with the app closed. Title, body, and priority on the lock screen.

Emergency

Priority 2. Retries until you acknowledge.

Global Mute & Alert Snooze

Mute everything for 5 minutes to several hours when you need a break.

Inbox

Every firing and resolved alert in one searchable stream.

Alert details with history

Labels, timeline, and push/ack history for every incident.

Quiet Hours

Scheduled silence for sounds. Alerts still hit Inbox; critical can override.

Live updates

Live app updates and cross-device sync. No pull to refresh.

Configurable sounds

Different tones for emergency, firing, and resolved.

Comparison

Compared to Slack, email, and SMS

Where Handler differs from the channels most teams already use for alerts.

Capability	Slack	Email	SMS
Push via APNs & FCM			—
Emergency retry until ACK	—	—	—
Native Alertmanager fire & resolve	—	—	—
Inbox
Active Alerts	—	—	—
Alert detail with full history	—	—	—
Rich notifications	—	—	—
Customizable sounds & settings	—	—	—
Customizable Quiet Hours	—	—	—
Live / cross-device sync			—

Frequently asked questions

Handler exists so important alerts can cut through everyday notification noise. Slack and Discord webhooks don't have that punch for on-call.

I built Handler from my own DevOps and homelab needs: easy to send, hard to miss on the phone.

Get started free