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