Transparency alternatives to Mage
Other Data integration vendors we measure, sorted by how much they publish that Mage does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 48 that differ from Mage on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Mage has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Mage does not” is the one that closes them.
| Vendor | Score | Publishes, and Mage does not | Mage publishes, and they do not | |
|---|---|---|---|---|
| Estuaryestuary.dev | 65/100 | 5 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +2 | 1 Data location stated | Compare |
| Prefectprefect.io | 65/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 Data location stated | Compare |
| Matillionmatillion.com | 61/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Astronomerastronomer.io | 52/100 | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Keboolakeboola.com | 52/100 | 4 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Captain Datacaptaindata.com | 48/100 | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | 2 Data location stated, Certifications named | Compare |
| Riveryrivery.io | 43/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | Compare |
| Snowplowsnowplow.io | 43/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | Compare |
| Hevo Datahevodata.com | 52/100 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Nimblewaynimbleway.com | 39/100 | 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact | 2 Data location stated, Certifications named | Compare |
| Redpandaredpanda.com | 39/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 2 Data location stated, Public pricing | Compare |
| Ducodu.co | 35/100 | 3 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change | 3 Data location stated, Public pricing, Certifications named | 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.