Transparency alternatives to OhDear
Other Incident management vendors we measure, sorted by how much we found at them and not at OhDear. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from OhDear on at least one criterion we measured for both. Public transparency score, not a product or security rating.
OhDear has 5 gaps in what we could measure: Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at OhDear” is the one that closes them.
| Vendor | Score | Found there, not found at OhDear | Found at OhDear, not found there | |
|---|---|---|---|---|
| Hyperpinghyperping.ioSee also Transparency alternatives to Hyperping | 74/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Notice before subprocessors change | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| incident.ioincident.ioSee also Transparency alternatives to incident.io | 65/100 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Moogsoftmoogsoft.comSee also Transparency alternatives to Moogsoft | 61/100 | 3 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data processing agreement, Public pricing, security.txt (RFC 9116) | Compare |
| BigPandabigpanda.ioSee also Transparency alternatives to BigPanda | 48/100 | 3 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change | 5 Data processing agreement, Data location stated, Certifications named, +2 | Compare |
| Resolveresolve.ioSee also Transparency alternatives to Resolve | 57/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data processing agreement, Certifications named, security.txt (RFC 9116) | Compare |
| Rootlyrootly.comSee also Transparency alternatives to Rootly | 48/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Subprocessor list, Certifications named | Compare |
| Uptime.comuptime.comSee also Transparency alternatives to Uptime.com | 48/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| AlertOpsalertops.comSee also Transparency alternatives to AlertOps | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | Compare |
| ilertilert.comSee also Transparency alternatives to ilert | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | Compare |
| Instatusinstatus.comSee also Transparency alternatives to Instatus | 39/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 5 Subprocessor list, Data location stated, Certifications named, +2 | Compare |
| Causelycausely.aiSee also Transparency alternatives to Causely | 35/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | Compare |
| Sorrysorryapp.comSee also Transparency alternatives to Sorry | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 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.