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