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