pgvector vs Qdrant

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

	pgvector Postgres extension for vector similarity search.	Qdrant Rust-based vector similarity search engine and database with payload filtering.
Category	retrieval	retrieval
Vendor type	open source	hybrid
Pricing	free	freemium
Strengths	+ Use the database you already run + Open source + Transactional consistency with relational data	+ 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
Tradeoffs	− Single-machine scaling limits vs purpose-built vector DBs	− 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
Used in stacks	4	0