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