Transparency alternatives to Valyu
Other Search and vector infrastructure vendors we measure, sorted by how much they publish that Valyu does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Valyu on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Valyu has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Valyu does not” is the one that closes them.
| Vendor | Score | Publishes, and Valyu does not | Valyu publishes, and they do not | |
|---|---|---|---|---|
| Chromatrychroma.com | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 security.txt (RFC 9116) | Compare |
| Pineconepinecone.io | 70/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 1 security.txt (RFC 9116) | Compare |
| Vectaravectara.com | 65/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Gleanglean.com | 39/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Hebbiahebbia.ai | 39/100 | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Zillizzilliz.com | 30/100 | 4 Status page with history, Certifications named, Uptime SLA with a figure, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Dashworksdashworks.ai | 43/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Constructorconstructor.com | 39/100 | 3 Data processing agreement, Data location stated, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Voyage AIvoyageai.com | 39/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Vespavespa.ai | 35/100 | 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact | 1 Public pricing | Compare |
| Marqomarqo.ai | 30/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Nostonosto.com | 30/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 3 Public pricing, HTTPS enforced with HSTS, 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.