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