Transparency alternatives to Dash0
Other Monitoring and observability vendors we measure, sorted by how much they publish that Dash0 does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from Dash0 on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dash0 has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Dash0 does not” is the one that closes them.
| Vendor | Score | Publishes, and Dash0 does not | Dash0 publishes, and they do not | |
|---|---|---|---|---|
| Honeycombhoneycomb.io | 70/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Sentrysentry.io | 74/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 HTTPS enforced with HSTS | Compare |
| Rollbarrollbar.com | 70/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Pulseticpulsetic.com | 65/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Datadogdatadoghq.com | 61/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| OpenObserveopenobserve.ai | 61/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| New Relicnewrelic.com | 57/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 2 Data location stated, Certifications named | Compare |
| Sumo Logicsumologic.com | 57/100 | 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| OneUptimeoneuptime.com | 52/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Chronospherechronosphere.io | 26/100 | 3 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change | 5 Data location stated, Public pricing, Certifications named, +2 | Compare |
| Better Stackbetterstack.com | 57/100 | 2 Data processing agreement, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| UptimeRobotuptimerobot.com | 57/100 | 2 Data processing agreement, Notice before subprocessors change | 1 security.txt (RFC 9116) | 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.