Qdrant vs turbopuffer

Pick two tools from the same category to compare side-by-side.

	Qdrant Rust-based vector similarity search engine and database with payload filtering.	turbopuffer Serverless vector + full-text search with object-storage backend.
Category	retrieval	retrieval
Vendor type	hybrid	commercial
Pricing	freemium	usage
Strengths	+ Single-stage metadata filtering during HNSW traversal rather than pre/post-filtering + Quantization options (scalar, product, binary) cut memory footprint substantially + Native hybrid search with dense, sparse, and late-interaction reranking + Rust implementation with REST/gRPC APIs and official Python/JS clients	+ Object-storage-backed; cheap at rest + Hybrid vector + BM25 search + Per-namespace isolation
Tradeoffs	− No built-in embedding modules historically; you manage vectorization yourself (cloud inference is newer) − Distributed mode requires manual sharding and replication decisions compared to fully elastic systems − Less natural fit than pgvector for teams wanting vectors inside an existing Postgres stack	− Newer player; smaller ecosystem than Pinecone
Used in stacks	0	13