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