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