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