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