Transparency alternatives to PagerDuty
Other Incident management vendors we measure, sorted by how much we found at them and not at PagerDuty. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from PagerDuty on at least one criterion we measured for both. Public transparency score, not a product or security rating.
PagerDuty has 7 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at PagerDuty” is the one that closes them.
| Vendor | Score | Found there, not found at PagerDuty | Found at PagerDuty, not found there | |
|---|---|---|---|---|
| Hyperpinghyperping.ioSee also Transparency alternatives to Hyperping | 74/100 | 4 Data processing agreement, Data location stated, Uptime SLA with a figure, +1 | 1 Named privacy contact | Compare |
| incident.ioincident.ioSee also Transparency alternatives to incident.io | 65/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 Named privacy contact | Compare |
| Rootlyrootly.comSee also Transparency alternatives to Rootly | 48/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Moogsoftmoogsoft.comSee also Transparency alternatives to Moogsoft | 61/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| OhDearohdear.appSee also Transparency alternatives to OhDear | 61/100 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | 1 Notice before subprocessors change | Compare |
| All Quietallquiet.appSee also Transparency alternatives to All Quiet | 48/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Everbridgeeverbridge.comSee also Transparency alternatives to Everbridge | 48/100 | 3 Data processing agreement, Data location stated, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| ilertilert.comSee also Transparency alternatives to ilert | 43/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Resolveresolve.ioSee also Transparency alternatives to Resolve | 57/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Certifications named | Compare |
| BigPandabigpanda.ioSee also Transparency alternatives to BigPanda | 48/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Certifications named, Named privacy contact | Compare |
| Instatusinstatus.comSee also Transparency alternatives to Instatus | 39/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Named privacy contact | Compare |
| Causelycausely.aiSee also Transparency alternatives to Causely | 35/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Subprocessor list, Notice before subprocessors change | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.