// comparison
inalarm against the on-call league
Honestly: where we stand strong and what we are still shipping. The “planned” fields are our roadmap, not fluff in a table.
| Feature | inalarm | PagerDuty | Opsgenie | incident.io |
|---|---|---|---|---|
| Escalation rules + time-based steps | yes | yes | yes | yes |
| Incident acknowledgement and takeover | yes | yes | yes | yes |
| SMS as a channel | yes | yes | yes | ? |
| Billing per on-call person, not per user | yes | no | no | no |
| VAT invoice, PL support, servers in PL | yes | no | no | no |
| On-call schedule and rotations | planned | yes | yes | yes |
| Wake-up phone call (voice) | planned | yes | yes | ? |
| Slack/Teams as incident hub | planned | yes | ? | yes |
// “?” = no confirmation in public materials, not a missing feature. We verify at the source before any sales call.