Transparency alternatives to Pulsetic
Other Monitoring and observability vendors we measure, sorted by how much they publish that Pulsetic does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Pulsetic on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Pulsetic has 5 gaps in what we could measure: Subprocessor list, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Pulsetic does not” is the one that closes them.
| Vendor | Score | Publishes, and Pulsetic does not | Pulsetic publishes, and they do not | |
|---|---|---|---|---|
| Sentrysentry.io | 74/100 | 3 Subprocessor list, Certifications named, security.txt (RFC 9116) | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| OpenObserveopenobserve.ai | 61/100 | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| OneUptimeoneuptime.com | 52/100 | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | 4 Data location stated, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | Compare |
| Honeycombhoneycomb.io | 70/100 | 2 Subprocessor list, Certifications named | 1 Data location stated | Compare |
| Rollbarrollbar.com | 70/100 | 2 Subprocessor list, Certifications named | 1 Data processing agreement | Compare |
| Datadogdatadoghq.com | 61/100 | 2 Subprocessor list, Certifications named | 2 Data location stated, Notice before subprocessors change | Compare |
| New Relicnewrelic.com | 57/100 | 2 Subprocessor list, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Sumo Logicsumologic.com | 57/100 | 2 Subprocessor list, Certifications named | 2 Data processing agreement, Data location stated | Compare |
| Checklychecklyhq.com | 39/100 | 2 Certifications named, Uptime SLA with a figure | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | Compare |
| Dash0dash0.com | 39/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | Compare |
| Splunksplunk.com | 39/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | Compare |
| Metorometoro.io | 35/100 | 2 Subprocessor list, Uptime SLA with a figure | 5 Data processing agreement, Data location stated, Status page with history, +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.