Transparency alternatives to Duco
Other Data integration vendors we measure, sorted by how much they publish that Duco does not. 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 “publishes and Duco does not” is the one that closes them.
| Vendor | Score | Publishes, and Duco does not | Duco publishes, and they do not | |
|---|---|---|---|---|
| Matillionmatillion.com | 61/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Weldweld.app | 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 |
| Astronomerastronomer.io | 52/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Hevo Datahevodata.com | 52/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Estuaryestuary.dev | 65/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | nothing | Compare |
| Prefectprefect.io | 65/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Keboolakeboola.com | 52/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 1 Subprocessor list | Compare |
| Captain Datacaptaindata.com | 48/100 | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Integrate.iointegrate.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.com | 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.io | 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 |
| Nimblewaynimbleway.com | 39/100 | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | 3 Subprocessor list, security.txt (RFC 9116), 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.