Transparency alternatives to Coveo
Other Search and vector infrastructure vendors we measure, sorted by how much we found at them and not at Coveo. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Coveo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Coveo has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Coveo” is the one that closes them.
| Vendor | Score | Found there, not found at Coveo | Found at Coveo, not found there | |
|---|---|---|---|---|
| Chromatrychroma.comSee also Transparency alternatives to Chroma | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Pineconepinecone.ioSee also Transparency alternatives to Pinecone | 70/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 security.txt (RFC 9116) | Compare |
| Parallelparallel.aiSee also Transparency alternatives to Parallel | 61/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Vectaravectara.comSee also Transparency alternatives to Vectara | 61/100 | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Dashworksdashworks.aiSee also Transparency alternatives to Dashworks | 43/100 | 3 Data location stated, Public pricing, Certifications named | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Addsearchaddsearch.comSee also Transparency alternatives to Addsearch | 39/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Gleanglean.comSee also Transparency alternatives to Glean | 39/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Hebbiahebbia.aiSee also Transparency alternatives to Hebbia | 39/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Zillizzilliz.comSee also Transparency alternatives to Zilliz | 30/100 | 3 Public pricing, Certifications named, Uptime SLA with a figure | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Constructorconstructor.comSee also Transparency alternatives to Constructor | 39/100 | 2 Data processing agreement, Data location stated | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Voyage AIvoyageai.comSee also Transparency alternatives to Voyage AI | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Cludocludo.comSee also Transparency alternatives to Cludo | 35/100 | 2 Data location stated, Public pricing | 2 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.