← PushPig
Server & monitoring alerts
Warnings from scripts, cron jobs and monitoring, to your device in real time.
When a server goes down, a disk fills up or a backup fails, every minute counts. With
PushPig you send server and monitoring alerts to your phone in
real time, from any script, cron job or monitoring tool that can make an HTTP request.
Alert from any script
A single curl call is enough. Drop it into health checks, backup scripts or cron jobs
and get notified the moment something breaks:
#!/bin/bash
if ! curl -fsS https://api.example.com/health > /dev/null; then
curl -X POST https://pushpig.de/api/push/send \
-H "Authorization: Bearer pp_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"channel":"ops","title":"API down","body":"Health check failed","urgent":true}'
fi
Connect your monitoring tools
Prometheus Alertmanager, Grafana, Uptime-Kuma & co. can fire alerts via webhook. The target
URL is simply the PushPig endpoint /api/push/send. Existing alerts land on all your
team's devices without a detour: Android app, browser and email.
Urgent means urgent
Critical alerts must not get stuck in a quiet window. With "urgent": true the push
bypasses every recipient's quiet hours and is delivered immediately. Routine
messages still respect them.
Finely scoped: with
API key scopes a server key can write only to
the
ops channel. If it leaks, the damage is contained.
Why PushPig for alerts
- No app store needed: web push, Android and email fallback in one API
- Rate limits and per-alert delivery status (how many devices were reached)
- Servers in the EU, GDPR-compliant: a fit for internal ops data
Frequently asked questions
How do I get a server alert onto my phone?
With a single HTTP POST to /api/push/send, fired from the script that notices the failure. The alert reaches every subscriber of the channel within seconds, via the Android app, the browser and, if push fails, by email.
Can I hook up Prometheus, Grafana or Uptime Kuma?
Yes. All three can fire alerts as webhooks. Set the target URL to the PushPig endpoint /api/push/send and add your API key as an Authorization header. Your existing alert rules stay as they are.
How do I make sure a critical alert arrives at night?
Set "urgent": true in the request. Those pushes bypass every recipient's quiet hours and are delivered immediately, while routine messages without the flag keep respecting them.
How do I limit the damage if a server key is stolen?
With API key scopes. A key scoped to push:send:42 can send to that one channel and nothing else, so a compromise stays contained and you only have to rotate that key.
Can I see whether the alert actually arrived?
Yes. The send API's response reports the number of recipients reached per delivery path: fcm_sent for Android, webpush_sent for browsers, email_sent for the email fallback. The same numbers appear in the channel feed.
Help & API ·
Pricing ·
Contact ·
Imprint ·
Privacy