Alternatives to Rootly
Other Incident management vendors we measure, sorted by how much they publish that Rootly does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Rootly on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Rootly has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Rootly does not” is the one that closes them.
| Vendor | Score | Publishes, and Rootly does not | Rootly publishes, and they do not | |
|---|---|---|---|---|
| Hyperpinghyperping.io | 74/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| incident.ioincident.io | 65/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 2 Data location stated, Named privacy contact | Compare |
| ilertilert.com | 70/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Moogsoftmoogsoft.com | 61/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| OhDearohdear.app | 61/100 | 3 Data processing agreement, Subprocessor list, Certifications named | 1 HTTPS enforced with HSTS | Compare |
| Uptime.comuptime.com | 48/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Data location stated, security.txt (RFC 9116) | Compare |
| PagerDutypagerduty.com | 39/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| All Quietallquiet.app | 48/100 | 2 Data processing agreement, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Causelycausely.ai | 48/100 | 2 Certifications named, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| BigPandabigpanda.io | 39/100 | 2 Subprocessor list, Notice before subprocessors change | 4 Data location stated, Public pricing, security.txt (RFC 9116), +1 | Compare |
| Everbridgeeverbridge.com | 39/100 | 2 Data processing agreement, Certifications named | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Jelijeli.io | 30/100 | 2 Subprocessor list, Notice before subprocessors change | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 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.