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