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