StatOSS compared with PagerDuty
PagerDuty sells incident management from $21 a user a month. StatOSS sells on-call for one person at $4 and for a team at $15, takes PagerDuty's Events API, and makes no phone calls.
curl -X POST https://api.statoss.com/v2/enqueue \
-H "Content-Type: application/json" \
-d '{"routing_key": "<the source's key>",
"event_action": "trigger",
"payload": {"summary": "Checkout error rate above 5%",
"source": "checkout", "severity": "critical"}}'Side by side
| StatOSS | PagerDuty | |
|---|---|---|
| Free | No on-call on Free | 5 users, 1 on-call schedule, 1 escalation policy, limited email, push, SMS and phone |
| Paid | Hobby $4 a month: 3 sources, one person. Pro $15: 50 sources, escalation, schedules, 3 people, $5 each after, up to 25 | Professional: $25 per user a month, $21 billed annually |
| Platform tiers | None | PD Reliability Platform from $2,800 a year with 10 seats and 5,000 events |
| Phone and SMS | None: email, Pushover, ntfy, Telegram, Slack | Included, limited on Free |
| Status pages | Included, with the checks | An add-on, purchased separately |
| Events API | Takes PagerDuty's Events API at api.statoss.com | Its own |
| Import | Schedules, escalation policies and integrations from a PagerDuty account, on Pro | n/a |
Facts about the other product were read from its own site on 11 October 2026. Prices and limits change; check theirs before deciding, and tell [email protected] if something here is out of date.
When PagerDuty is the better pick
Phone calls, SMS, live call routing, post-incident reviews and the integrations a large organisation runs on: PagerDuty has them and StatOSS does not.
Where StatOSS fits: a team of a few people that wants on-call, a status page and the checks on one $15 bill, with no per-user price.
Moving over
On Pro, a read-only PagerDuty key imports schedules, escalation policies and integrations after a preview. A sender changes only the host, to api.statoss.com. The import section of the docs has the steps.