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