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