mem1.wiki

Tools

Tool

Qdrant

Open-source vector database written in Rust. Strong payload filtering, hybrid (sparse + dense) search, and a managed cloud option. Default-OK choice for most RAG stacks.

URL
https://github.com/qdrant/qdrant
Taxonomy
tools.memory.vector_dbs
License
Apache-2.0
Hosting
hybrid
Pricing
open_core
Status
active
Language
rust
Stars
23,000
First release
2021
Self-host difficulty
trivial
Tags
vector-db, hnsw, rust, payload-filtering

What it is

Qdrant is a vector similarity engine with a REST/gRPC API and a Rust core. It treats payload (structured metadata) as a first-class citizen — you can filter by payload before or after the ANN search, which closes a lot of the gap between “pure vector DB” and a search engine.

Where it fits

Trade-offs

How Qdrant compares

AI-generated editorial comparisons against nearest peers (glm-4.6). Cached at build time; regenerate via node scripts/build-comparisons.mjs.

vs Mem0AI · cached

Mem0 is a specialized memory layer for agents, whereas Qdrant is a general-purpose vector database for retrieval. Mem0 handles the lifecycle of conversational facts—extracting "user prefers dark mode," decaying unused context, and surfacing it automatically in chat loops. It is strictly for maintaining state in long-running assistants or personal CRMs, and it fails for static knowledge retrieval. Do not use it for one-shot RAG over a company PDF corpus, as it lacks the infrastructure for large-scale document chunking.

Qdrant wins for raw RAG stacks and GraphRAG because it prioritizes high-performance search over conversational state. Its filtering engine allows you to mix dense vectors with sparse BM25 data, which is critical when you need to constrain search by metadata (like "filter by date"). However, Qdrant requires manual orchestration; you must write your own extractors and ingestion pipelines. If you need a drop-in memory that manages itself, use Mem0. If you need to query millions of vectorized documents with complex filters, use Qdrant.