Qdrant

Qdrant is a fast, open-source vector database written in Rust for similarity search, hybrid filtering, and AI workloads like RAG and recommendations. We rate it 87/100 — for teams that have outgrown pgvector and need first-class metadata filtering with a clean Rust core, Qdrant is one of the best choices on the market today.

What is Qdrant?

Qdrant (pronounced "quadrant") is an open-source vector search engine and managed cloud service built specifically for storing, indexing and querying high-dimensional embeddings. It was founded in May 2021 in Berlin by CEO Andre Zayarni and CTO Andrey Vasnetsov, who previously built recommendation and search systems and felt existing options were either too slow, too memory-hungry, or bolted onto general-purpose databases.

The core engine is licensed Apache 2.0, runs as a single self-contained binary, exposes both REST and gRPC APIs, and is deployable as Docker, Kubernetes (via the official Helm chart and Operator), or a managed cluster on Qdrant Cloud across AWS, GCP and Azure. As of 2026 the company has raised roughly $87.8M across four rounds and reports tens of thousands of production deployments.

Key Features of Qdrant

• Rust-native HNSW engine: Qdrant ships its own HNSW implementation with filterable graph traversal, so metadata filters are applied during the ANN search instead of post-filtering — which is why complex filtered queries stay fast where naive vector DBs collapse.
• Hybrid & sparse search: Native support for dense + sparse vectors (BM25, SPLADE), multi-vector queries, and named vectors per point — useful for hybrid retrieval pipelines without bolting on a second engine.
• Quantization built-in: Scalar, product, and binary quantization can shrink memory by up to 32× with minimal recall loss, and the docs include real recall/latency numbers for each setting.
• Distributed deployment: Sharding, replication, and consensus via Raft come out of the box; clusters can be resized horizontally on Cloud or self-hosted.
• Cloud Inference (2025+): Qdrant Cloud now embeds first-party inference for popular models so you can index and query without a separate embedding service.
• SOC 2, GDPR, HIPAA: The managed offering covers the compliance boxes most enterprises need before procurement will sign.

What Users Say About Qdrant

Sentiment in the developer community is generally positive but nuanced. On the Hacker News thread for Qdrant's $28M Series A, top commenters praise the Rust core, the clean API, and the fact that the docs are \"clear and to the point\" — the team's active engagement on issues is a recurring theme. Developers on r/MachineLearning and r/LocalLLaMA frequently recommend Qdrant for production RAG over pgvector when filtering complexity grows.

The honest complaints are also consistent. Initial bulk ingestion can be finicky on very large datasets (people report needing to tune segments and batch sizes carefully). Operationally, Qdrant has a higher learning curve than \"just use Postgres\" — for small workloads pgvector or pgvectorscale is often the pragmatic choice, and a 2026 Tigerdata benchmark showed pgvectorscale hitting 471 QPS at 99% recall on 50M vectors versus Qdrant's 41 QPS in their specific setup. Other independent benchmarks (CallSphere, ZenML) show Qdrant ahead on filtered queries and competitive on raw ANN — so the picture is workload-dependent, not a clean win for either side.

Qdrant Pricing

Qdrant has one of the friendliest pricing structures among hosted vector databases. The self-hosted engine is fully Apache 2.0 with no feature gating; the managed Cloud has a permanent free tier (no credit card) and pay-as-you-go above it.

Plan	Price	Key Limits
Self-hosted (Community)	Free / Apache 2.0	Unlimited; you run the binary or Docker image
Cloud Free	$0 / month	1 GB RAM, 4 GB disk, 0.5 vCPU, single-node cluster — no card required
Cloud Standard	From ~$0.014 / hour (~$25 / month entry)	Dedicated multi-node clusters, backups, monitoring, auto-scaling
Hybrid Cloud	Usage-based	Run Qdrant in your own VPC / cluster, managed by Qdrant's control plane
Private Cloud / Enterprise	Contact sales	Air-gapped, BYO Kubernetes, dedicated support, SOC 2 / HIPAA

Who Should Use Qdrant?

Best for: ML and platform engineers building production RAG, semantic search or recommendation systems where you need (a) heavy metadata filtering, (b) more than ~10M vectors, or (c) the ability to run the same engine locally, in your VPC, and on a managed cloud. It's also a strong default for teams that prefer a real database over a Python library wrapping FAISS.

Not ideal for: Hobby projects with a few thousand vectors (use pgvector or SQLite-vss), teams already deeply on Postgres who don't need cross-cloud portability, or anyone who wants embeddings, ranking and a UI all bundled (a hosted RAG platform may be a better fit).

Pros and Cons

Pros:

• Truly open-source core (Apache 2.0) with no \"open-core\" feature lockout.
• Filtering is integrated into the HNSW traversal — measurably faster on filtered workloads than post-filter approaches.
• Clean, well-documented REST and gRPC APIs with first-party Python, JS, Rust, Go, Java and .NET clients.
• Generous free Cloud tier (1 GB RAM, no card) and per-hour pricing above that.
• Active community and noticeably responsive maintainers on GitHub and Discord.

Cons:

• Bulk ingestion of very large datasets can require manual tuning of segments, batch sizes and quantization settings.
• Operational footprint is higher than \"just add a column to Postgres\" — pgvector / pgvectorscale will win on simplicity for small-to-mid workloads.
• Distributed clustering is solid but younger than the rest of the engine; ops tooling (UI, observability dashboards) still maturing.
• No bundled embedding model UI — you bring your own embeddings (Cloud Inference helps but is not yet at parity with dedicated providers).

Alternatives to Qdrant

The main competitors are Weaviate (richer schema and modules, Go-based), Milvus (battle-tested at billion-scale but heavier to operate), pgvector / pgvectorscale (just-use-Postgres simplicity, excellent for small-to-mid workloads), and managed services like Pinecone (closed-source, more expensive, very low-touch). For most teams the real decision is Qdrant vs pgvector vs Pinecone — Qdrant sits in the sweet spot of \"open-source, fast, filterable, runs anywhere.\"

Verdict: Is Qdrant Worth It?

Yes, for the right workload. If you're shipping production RAG or semantic search, expect to pass tens of millions of vectors, and need real filtering — Qdrant is one of the strongest choices available today, and the fact that the same engine runs locally, in your VPC, and on Qdrant Cloud is genuinely valuable. We rate it 87/100 — knocked off the very top tier only because operational maturity and large-scale ingestion still trail the most polished managed offerings, and because for the smallest workloads pgvector remains the more pragmatic default.

Frequently Asked Questions

Is Qdrant free?

Yes. The Qdrant engine is Apache 2.0 open-source and free to self-host with no feature gating. Qdrant Cloud also has a permanent free tier (1 GB RAM, 4 GB disk, 0.5 vCPU) with no credit card required. Paid Standard clusters start at about $0.014/hour.

What platforms does Qdrant support?

Qdrant runs on Linux, macOS and Windows as a single binary or Docker image, and is deployable on AWS, GCP, Azure, any Kubernetes cluster, and at the edge. Client SDKs are official for Python, JavaScript/TypeScript, Rust, Go, Java and .NET.

How does Qdrant compare to Pinecone?

Pinecone is a fully managed closed-source service that's very low-touch but more expensive at scale. Qdrant is open-source and gives you the choice of self-hosting, managed Cloud, or hybrid — with comparable or better performance on filtered workloads in most third-party benchmarks.

How does Qdrant compare to pgvector?

pgvector is a Postgres extension and is excellent up to a few million vectors with simple filters. Qdrant is purpose-built and tends to win on filtered queries, quantization, hybrid sparse+dense search, and very large collections — at the cost of running another service.

Is Qdrant open source?

Yes. The full Qdrant engine is licensed Apache 2.0. Source code is at github.com/qdrant/qdrant.