Transparency alternatives to Gresham
Other Data catalogs and governance vendors we measure, sorted by how much they publish that Gresham does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Gresham on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Gresham has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Gresham does not” is the one that closes them.
| Vendor | Score | Publishes, and Gresham does not | Gresham publishes, and they do not | |
|---|---|---|---|---|
| Privaceraprivacera.com | 57/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 Named privacy contact | Compare |
| Metaplanemetaplane.dev | 48/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | nothing | Compare |
| Anomaloanomalo.com | 48/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | nothing | Compare |
| Satorisatoricyber.com | 43/100 | 3 Data location stated, Status page with history, No third-party tracking before consent | nothing | Compare |
| Immutaimmuta.com | 39/100 | 3 Data location stated, Status page with history, Certifications named | nothing | Compare |
| Bigeyebigeye.com | 35/100 | 3 Status page with history, Certifications named, Notice before subprocessors change | nothing | Compare |
| Lightuplightup.ai | 35/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| Validiovalidio.io | 30/100 | 2 Data processing agreement, Certifications named | nothing | Compare |
| Datagalaxydatagalaxy.com | 22/100 | 2 Data location stated, Certifications named | 1 HTTPS enforced with HSTS | Compare |
| DataHubdatahub.com | 22/100 | 2 Data processing agreement, Notice before subprocessors change | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| Preciselyprecisely.com | 17/100 | 2 Status page with history, security.txt (RFC 9116) | 1 HTTPS enforced with HSTS | Compare |
| Colectica Repositorycolectica.com | 22/100 | 1 Data location stated | 1 Named privacy contact | 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.