Qdrant
Rust-fast open-source vector engine. Cleaner API than Weaviate, smaller footprint.
VISIT QDRANTQuick facts
- CategorySelf-hosted
- EngineRust
- PricingFreemium
- LicenseApache-2.0
- Created2020
- GitHub stars28.4k
- Hybrid searchNative
- Edge-readyNo
- Multi-tenantNative
- Max dimensions65,535
What it is
Qdrant is a Rust-based open-source vector database. Cleaner API and simpler operational model than Weaviate, strong filter performance (filterable HNSW indexes are a real differentiator), Qdrant Cloud for managed hosting. Used heavily in production AI deployments where latency at scale matters.
Best for
- Latency-critical RAG workloads
- Apps with heavy filtered search (filter by user_id, tenant, time, then vector-rank)
- Self-host-first teams who value Rust's performance and operational simplicity
When not to pick it
Skip Qdrant if hybrid search (vector + keyword) is the deciding feature — Weaviate is stronger there. Skip for very small workloads where pgvector suffices.
My take
Qdrant is the right pick for self-hosted vector at scale when filtering is the hot path. Rust performance is real; the API is cleaner than the alternatives.
Links
Compare Qdrant side-by-side
Similar tools you should also consider
Weaviate
Open-source self-hostable vector database with hybrid search and module ecosystem.
Read the take →Milvus
Distributed vector DB built for billion-scale workloads. Heavy, capable, China-AI-aligned.
Read the take →pgvector
Vector search inside Postgres. The default for teams already on Postgres or Supabase.
Read the take →If Qdrant is your pick — the next conversation is short
The 30-min call is where your vector-DB choice becomes a real RAG architecture, a chunking + reranking strategy that actually works for your corpus, and a price range you can take to your stakeholders. Describe your data shape, your query patterns, your latency budget. I tell you whether Qdrant is genuinely your fit.