Alternatives to Segment
Other Data integration vendors we measure, sorted by how much they publish that Segment does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Segment on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Segment has 5 gaps in what we could measure: Data processing agreement, Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Segment does not” is the one that closes them.
| Vendor | Score | Publishes, and Segment does not | Segment publishes, and they do not | |
|---|---|---|---|---|
| Keboolakeboola.com | 65/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | Compare |
| Estuaryestuary.dev | 80/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 1 Uptime SLA with a figure | Compare |
| Prefectprefect.io | 80/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 1 Uptime SLA with a figure | Compare |
| Weldweld.app | 57/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 4 Subprocessor list, Uptime SLA with a figure, Notice before subprocessors change, +1 | Compare |
| Hevo Datahevodata.com | 55/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| Astronomerastronomer.io | 52/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Data location stated, Status page with history | Compare |
| Redpandaredpanda.com | 52/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Status page with history, Uptime SLA with a figure, +1 | Compare |
| Confluentconfluent.io | 40/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Y42y42.com | 40/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Striimstriim.com | 58/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Status page with history, Certifications named | Compare |
| Hightouchhightouch.com | 55/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Status page with history, Uptime SLA with a figure | Compare |
| Matillionmatillion.com | 55/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Subprocessor list, Uptime SLA with a figure | 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.