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