Transparency alternatives to Confluent
Other Data integration vendors we measure, sorted by how much we found at them and not at Confluent. This is a comparison of disclosure, not of features or fitness.
12 shown of 47 that differ from Confluent on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Confluent has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, 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 Confluent” is the one that closes them.
| Vendor | Score | Found there, not found at Confluent | Found at Confluent, not found there | |
|---|---|---|---|---|
| Estuaryestuary.devSee also Transparency alternatives to Estuary | 65/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 1 Data location stated | Compare |
| Prefectprefect.ioSee also Transparency alternatives to Prefect | 65/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Matillionmatillion.comSee also Transparency alternatives to Matillion | 61/100 | 5 Data processing agreement, Status page with history, Certifications named, +2 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Astronomerastronomer.ioSee also Transparency alternatives to Astronomer | 52/100 | 5 Data processing agreement, Certifications named, Uptime SLA with a figure, +2 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Snowplowsnowplow.ioSee also Transparency alternatives to Snowplow | 43/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Keboolakeboola.comSee also Transparency alternatives to Keboola | 52/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| RudderStackrudderstack.comSee also Transparency alternatives to RudderStack | 48/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Riveryrivery.ioSee also Transparency alternatives to Rivery | 43/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Weldweld.appSee also Transparency alternatives to Weld | 57/100 | 3 Data processing agreement, Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Hevo Datahevodata.comSee also Transparency alternatives to Hevo Data | 52/100 | 3 Status page with history, Certifications named, Named privacy contact | nothing | Compare |
| Captain Datacaptaindata.comSee also Transparency alternatives to Captain Data | 43/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Redpandaredpanda.comSee also Transparency alternatives to Redpanda | 39/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 2 Data location stated, Public pricing | 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.