SaaS Ranking

Transparency alternatives to Splunk

Other Monitoring and observability vendors we measure, sorted by how much we found at them and not at Splunk. This is a comparison of disclosure, not of features or fitness.

12 shown of 44 that differ from Splunk on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Splunk 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 “Found there, not found at Splunk” is the one that closes them.

VendorScoreFound there, not found at SplunkFound at Splunk, not found there
Honeycombhoneycomb.ioSee also Transparency alternatives to Honeycomb 70/100 5 Data processing agreement, Subprocessor list, Status page with history, +2 2 Data location stated, security.txt (RFC 9116) Compare
OpenObserveopenobserve.aiSee also Transparency alternatives to OpenObserve 70/100 5 Data processing agreement, Subprocessor list, Status page with history, +2 2 Data location stated, security.txt (RFC 9116) Compare
Sentrysentry.ioSee also Transparency alternatives to Sentry 74/100 4 Data processing agreement, Subprocessor list, Status page with history, +1 1 HTTPS enforced with HSTS Compare
Pulseticpulsetic.comSee also Transparency alternatives to Pulsetic 65/100 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 2 Certifications named, security.txt (RFC 9116) Compare
Datadogdatadoghq.comSee also Transparency alternatives to Datadog 61/100 4 Data processing agreement, Subprocessor list, Status page with history, +1 2 Data location stated, 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 2 Data location stated, Certifications named Compare
Sumo Logicsumologic.comSee also Transparency alternatives to Sumo Logic 57/100 4 Subprocessor list, Status page with history, Notice before subprocessors change, +1 2 Data location stated, security.txt (RFC 9116) Compare
OneUptimeoneuptime.comSee also Transparency alternatives to OneUptime 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.ioSee also Transparency alternatives to Chronosphere 35/100 4 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change, +1 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 Compare
Rollbarrollbar.comSee also Transparency alternatives to Rollbar 64/100 3 Subprocessor list, Notice before subprocessors change, Named privacy contact nothing Compare
Netdatanetdata.cloudSee also Transparency alternatives to Netdata 52/100 3 Status page with history, Uptime SLA with a figure, Named privacy contact 1 security.txt (RFC 9116) Compare
Better Stackbetterstack.comSee also Transparency alternatives to Better Stack 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.