Qdrant

Qdrant is an open-source vector database written in Rust. It stores embeddings, attaches payload metadata, and searches vectors with filters for RAG, semantic search, recommendations, and AI-native retrieval systems.

It is one of the main open-source alternatives to Pinecone and Weaviate.

When to pick Qdrant

• You want self-hosting. Run Qdrant in your own environment when data control matters.
• Payload filtering matters. Many RAG systems need metadata-aware retrieval, not pure vector similarity.
• You like a focused database. Qdrant does not try to be a full app platform.
• You may need cloud later. Qdrant Cloud gives a managed option without switching databases.
• You are building internal retrieval services. The API is straightforward for service teams.

When to pick something else

• Most managed production default: Pinecone.
• Broader AI-native vector platform: Weaviate.
• App database plus vectors: pgvector in Postgres.
• Enterprise search and assistant: Glean.

How to evaluate it

Evaluate Qdrant with the retrieval workload you actually have, not with a generic vector benchmark. The important questions are filter selectivity, recall at your target latency teams should test chunk metadata, hybrid retrieval strategy, and re-ranking outside the database before treating any vector store as the full search system.

Qdrant is a strong fit when the team wants infrastructure control. Self-hosting keeps deployment choices open, while Qdrant Cloud reduces operational burden for teams that do not want to run clusters themselves. The simpler product scope can be an advantage: fewer platform assumptions, clearer database behavior, and less pressure to adopt a full enterprise search suite.

Choose something else if your hardest problem is connectors, permissions, or end-user UX. Glean-style workplace search tools solve a different layer. Weaviate is stronger when you want a broader vector platform with hybrid search and managed-cloud packaging. Pinecone is stronger when a cloud-native managed service is the default priority.

Pricing

Self-hosting Qdrant is free apart from infrastructure costs. Qdrant Cloud now has a clearer public tier shape:

Billing can run through credit card or AWS, GCP, and Azure marketplaces.

For small projects, self-hosting or pgvector may be cheaper. For production teams that value managed operations, Qdrant Cloud removes database maintenance work.

As verified on 2026-06-25, Qdrant’s cloud billing docs emphasize resource-shaped pricing rather than a simple per-query SaaS usage before procurement.

Evaluation checklist

Before committing to Qdrant:

• with your real chunking strategy.
• Measure metadata filter selectivity, not only nearest-neighbor speed.
• Decide whether hybrid search and reranking happen inside or outside the database layer.
• Plan backups, snapshots, upgrades, and monitoring before production launch.
• Confirm how tenant isolation maps to collections, payloads, or separate clusters.
• Benchmark pgvector for small Postgres-native apps before adding a separate vector database.
• Compare Qdrant Cloud against self-hosting once operations time is included.

Buyer fit

Qdrant is strongest for engineering teams that want a focused vector database with open-source optionality. It is a good match when the product team owns retrieval quality and wants control over deployment, payload schema, filters, and evaluation.

It is weaker when the buyer expects a finished knowledge product. Qdrant will not connect to every SaaS app, infer company permissions, or ship an employee-facing answer UI. It is the retrieval layer, not the entire enterprise-search system.