Transparency alternatives to Alation
Other Product information management vendors we measure, sorted by how much we found at them and not at Alation. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Alation on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Alation has 7 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Alation” is the one that closes them.
| Vendor | Score | Found there, not found at Alation | Found at Alation, not found there | |
|---|---|---|---|---|
| Sodasoda.ioSee also Transparency alternatives to Soda | 65/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 2 Subprocessor list, Named privacy contact | Compare |
| Siffletsiffletdata.comSee also Transparency alternatives to Sifflet | 52/100 | 3 Data processing agreement, Data location stated, Public pricing | 2 Subprocessor list, HTTPS enforced with HSTS | Compare |
| Reltioreltio.comSee also Transparency alternatives to Reltio | 39/100 | 3 Data location stated, Status page with history, Uptime SLA with a figure | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| data.worlddata.worldSee also Transparency alternatives to data.world | 39/100 | 2 Data location stated, Status page with history | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Ataccamaataccama.comSee also Transparency alternatives to Ataccama | 30/100 | 2 Public pricing, security.txt (RFC 9116) | 2 Subprocessor list, Notice before subprocessors change | Compare |
| DataFeedWatchdatafeedwatch.comSee also Transparency alternatives to DataFeedWatch | 30/100 | 2 Data location stated, Public pricing | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | Compare |
| Plytixplytix.comSee also Transparency alternatives to Plytix | 30/100 | 2 Data location stated, Public pricing | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Atlanatlan.comSee also Transparency alternatives to Atlan | 26/100 | 2 Data processing agreement, security.txt (RFC 9116) | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | Compare |
| Feedbirdfeedbird.comSee also Transparency alternatives to Feedbird | 26/100 | 2 Data location stated, Public pricing | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Fozzelsfozzels.comSee also Transparency alternatives to Fozzels | 26/100 | 2 Public pricing, security.txt (RFC 9116) | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Monte Carlomontecarlodata.comSee also Transparency alternatives to Monte Carlo | 26/100 | 2 Data processing agreement, security.txt (RFC 9116) | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | Compare |
| Akeneoakeneo.comSee also Transparency alternatives to Akeneo | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Subprocessor list, HTTPS enforced with HSTS, 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.