Pyyan / Compare / turbopuffer vs Weaviate
turbopuffer vs Weaviate
2 of 5Vector Databases · verified 13 Aug 2026
turbopufferturbopuffercurrent
WeaviateWeaviatecurrent| Specification | turbopuffer | Weaviate |
|---|---|---|
| Summary | Vectors on object storage, priced accordingly. | Hybrid search with batteries included. |
| Index | Proprietary, object storage | HNSW |
| Hybrid search | Yes | Yes, native |
| Hosting | Managed only | Self-host and managed |
| Licence | Proprietary | BSD-3 |
| p50 latency | ~20ms | ~12ms |
| Category | Vector Databases | Vector Databases |
| Official | turbopuffer ↗ | Weaviate ↗ |
Highlighted rows are where these differ.
turbopuffer
- Built on object storage rather than RAM
- Notion cut search costs ~60% moving from Pinecone Serverless
Best for large corpora where cost dominates.
Weaviate
- Vector, BM25 and metadata filters in one query
- Modules for embedding generation built in
Best for hybrid keyword and semantic search.