Transparency alternatives to Datadog
Other Monitoring and observability vendors we measure, sorted by how much we found at them and not at Datadog. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from Datadog on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Datadog has 5 gaps in what we could measure: Data location stated, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Datadog” is the one that closes them.
| Vendor | Score | Found there, not found at Datadog | Found at Datadog, not found there | |
|---|---|---|---|---|
| Sentrysentry.ioSee also Transparency alternatives to Sentry | 74/100 | 3 Data location stated, security.txt (RFC 9116), Notice before subprocessors change | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| OpenObserveopenobserve.aiSee also Transparency alternatives to OpenObserve | 70/100 | 2 Uptime SLA with a figure, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Pulseticpulsetic.comSee also Transparency alternatives to Pulsetic | 65/100 | 2 Data location stated, Notice before subprocessors change | 2 Subprocessor list, Certifications named | Compare |
| Rollbarrollbar.comSee also Transparency alternatives to Rollbar | 64/100 | 2 Data location stated, Notice before subprocessors change | 2 Data processing agreement, Status page with history | Compare |
| Better Stackbetterstack.comSee also Transparency alternatives to Better Stack | 57/100 | 2 Data location stated, Notice before subprocessors change | 3 Subprocessor list, Status page with history, Named privacy contact | Compare |
| New Relicnewrelic.comSee also Transparency alternatives to New Relic | 57/100 | 2 security.txt (RFC 9116), Notice before subprocessors change | 2 Data processing agreement, Certifications named | Compare |
| UptimeRobotuptimerobot.comSee also Transparency alternatives to UptimeRobot | 57/100 | 2 Data location stated, Notice before subprocessors change | 3 Subprocessor list, Status page with history, Named privacy contact | Compare |
| Netdatanetdata.cloudSee also Transparency alternatives to Netdata | 52/100 | 2 Data location stated, Uptime SLA with a figure | 2 Data processing agreement, Subprocessor list | Compare |
| Checklychecklyhq.comSee also Transparency alternatives to Checkly | 48/100 | 2 Data location stated, Uptime SLA with a figure | 3 Data processing agreement, Subprocessor list, Named privacy contact | Compare |
| Dash0dash0.comSee also Transparency alternatives to Dash0 | 39/100 | 2 Data location stated, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Splunksplunk.comSee also Transparency alternatives to Splunk | 39/100 | 2 Data location stated, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Chronospherechronosphere.ioSee also Transparency alternatives to Chronosphere | 35/100 | 2 Uptime SLA with a figure, Notice before subprocessors change | 4 Data processing agreement, Status page with history, Public pricing, +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.