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