Transparency alternatives to DataHub
Other Data catalogs and governance vendors we measure, sorted by how much we found at them and not at DataHub. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from DataHub on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DataHub has 10 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at DataHub” is the one that closes them.
| Vendor | Score | Found there, not found at DataHub | Found at DataHub, not found there | |
|---|---|---|---|---|
| Metaplanemetaplane.devSee also Transparency alternatives to Metaplane | 48/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Satorisatoricyber.comSee also Transparency alternatives to Satori | 43/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Immutaimmuta.comSee also Transparency alternatives to Immuta | 39/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Bigeyebigeye.comSee also Transparency alternatives to Bigeye | 35/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| Preciselyprecisely.comSee also Transparency alternatives to Precisely | 30/100 | 4 Subprocessor list, Status page with history, security.txt (RFC 9116), +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Anomaloanomalo.comSee also Transparency alternatives to Anomalo | 48/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Privaceraprivacera.comSee also Transparency alternatives to Privacera | 48/100 | 3 Data location stated, Status page with history, Certifications named | nothing | Compare |
| Validiovalidio.ioSee also Transparency alternatives to Validio | 30/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 1 Notice before subprocessors change | Compare |
| Datagalaxydatagalaxy.comSee also Transparency alternatives to Datagalaxy | 22/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Varonisvaronis.comSee also Transparency alternatives to Varonis | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Colectica Repositorycolectica.comSee also Transparency alternatives to Colectica Repository | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Acceldataacceldata.ioSee also Transparency alternatives to Acceldata | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data processing agreement, 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.