Qdrant
by Qdrant
Open-source vector search engine built in Rust for production AI retrieval
Qdrant is an open-source, Rust-built vector database for semantic search, retrieval-augmented generation and recommendation workloads at production scale. It combines dense, sparse and multi-vector retrieval with payload filtering applied during index traversal, and ships as a self-hosted binary, a managed cloud on AWS, GCP or Azure, a customer-run hybrid data plane, or an air-gapped private deployment.
Qdrant is an open-source vector search engine written entirely in Rust and licensed under Apache 2.0, built from first principles for vector retrieval rather than bolted onto a general-purpose database. It stores points — vectors carrying arbitrary JSON payloads — and serves approximate nearest-neighbour search over them through REST and gRPC APIs, with official Python and JavaScript clients and a browser UI for inspecting collections. Its distinguishing engineering choice is one-stage filtering: payload conditions are evaluated during HNSW graph traversal rather than before or after it, which keeps latency predictable on the heavily filtered queries that production RAG and recommendation systems actually issue. The engine handles dense, sparse and multi-vector search in a single query, giving native hybrid retrieval with BM25, SPLADE++ and miniCOIL support plus reranking via MMR and late-interaction models. Because memory dominates the cost of vector search, Qdrant ships scalar, binary and asymmetric quantization — the vendor claims up to 64x memory reduction — alongside a custom storage engine called Gridstore and real-time indexing that avoids full rebuilds; version 1.19 added the TurboQuant datatype and memory-tier optimisation. Distribution spans the full range: self-hosted Docker or Kubernetes, Qdrant Cloud managed on AWS, GCP and Azure, a Hybrid Cloud mode that decouples the control plane from a customer-operated data plane, an air-gapped Private Cloud, and Qdrant Edge in beta for on-device retrieval, with serverless announced but not yet shipped. The project reports more than 250 million package downloads and roughly 34,000 GitHub stars, and names Canva, HubSpot, Roche, Bosch, OpenTable, TripAdvisor and Deutsche Telekom among its users. It raised a $50M Series B led by Advance Venture Partners in March 2026, bringing total funding to $87.8M, and competes directly with Pinecone, Weaviate, Milvus and — increasingly — pgvector running inside an existing Postgres estate.
Platform and ML infrastructure teams running retrieval at tens of millions of vectors or more, who need filtered semantic search with predictable latency and a self-hosted or air-gapped deployment option their compliance team will accept.
Filtered vector search that stays fast at scale, with the same Apache-2.0 engine running on a laptop, in a managed cloud, or inside your own VPC — so there is no rewrite between prototype and production.
At a Glance
- Category
- Data & Analytics
- Pricing
- Usage-based, Freemium, Contact for pricing, Free
- Target Market
- CTOs, Platform Engineers, ML Engineers, Data Scientists, Enterprise Developers
- Deployment
- Open-source, Self-hosted, Cloud-first, Hybrid, Multi-cloud, Edge-first
- Headquarters
- Berlin, Germany
Key Features
- ✓One-stage filtered HNSW search
Applies payload filters during graph traversal instead of pre- or post-filtering, which avoids the recall collapse and latency spikes that filtered queries cause in naive vector indexes.
- ✓Native hybrid and multi-vector retrieval
Dense, sparse and multi-vector representations coexist in one collection and one query, supporting BM25, SPLADE++ and miniCOIL alongside embeddings without bolting on a second search system.
- ✓Quantization and Gridstore engine
Scalar, binary and asymmetric quantization backed by a purpose-built storage engine cut the RAM footprint that normally dominates vector database cost, with a claimed reduction of up to 64x.
- ✓Distributed sharding and replication
Horizontal sharding with replicas and zero-downtime upgrades lets a single cluster grow past the memory ceiling of one node into the billions of vectors.
- ✓Hybrid and Private Cloud deployment
A Kubernetes-based hybrid mode splits Qdrant's managed control plane from a data plane that never leaves customer infrastructure, and Private Cloud supports fully air-gapped installs.
- ✓Reranking and late interaction
Built-in MMR and late-interaction reranking refine the candidate set inside the database, removing a network hop and a separate reranker service from the retrieval path.
- ✓Real-time indexing with REST and gRPC APIs
New vectors become searchable without a full index rebuild, and both REST and gRPC interfaces ship with official Python and JavaScript clients plus a web UI.
Capabilities
Use Cases
- •Permission-aware enterprise RAG
Serve retrieval for an internal assistant where every query must be filtered by tenant, team and document ACL before results are returned to the model.
- •Product and catalogue semantic search
Replace keyword-only search with hybrid dense plus sparse retrieval so shoppers find items by description and intent, not exact token matches.
- •Agent long-term memory
Store conversation and tool-output embeddings so autonomous agents can recall prior context in sub-second lookups on every step of a run.
- •Content recommendation and deduplication
Compute nearest-neighbour similarity across millions of articles or listings to power related-item rails and to detect near-duplicate submissions at ingest.
- •On-device and edge retrieval
Run the beta Qdrant Edge build on resource-constrained hardware so retrieval works without a round trip to a central cluster.
Ideal For
Best For
- ✓Retrieval-augmented generation pipelines where every query carries tenant, permission or recency filters
- ✓Semantic and hybrid search over product catalogues, support content or document corpora at 10M+ vectors
- ✓Recommendation and similarity engines that need sub-second nearest-neighbour lookups on live data
- ✓Regulated deployments that require an air-gapped or in-VPC vector store rather than a multi-tenant SaaS
- ✓Agent memory stores where retrieval latency sits in the critical path of every tool call
Not Ideal For
- ✗Teams already running Postgres with under roughly 5 million vectors — pgvector delivers comparable query latency with zero new infrastructure, and Qdrant's advantage only appears at larger scale
- ✗Small teams without platform engineering capacity: running Qdrant means a second stateful service with its own snapshots, health checks, gRPC surface and release cadence to coordinate against the primary database
- ✗Applications that need transactional consistency between documents and their embeddings, since a split store can leave an unembedded document or an orphaned vector unless you add retries or a reconciliation job
- ✗Buyers who require published per-seat list pricing up front — the production tier is billed on hourly resource consumption rather than a quoted plan price
Integrations
Deployment
Market Analysis
Pros
- ✓Purpose-built Rust engine with SIMD acceleration outperforms general-purpose databases on raw vector throughput once datasets pass single-instance scale
- ✓Genuinely portable: Apache-2.0 self-hosted, managed cloud, hybrid data plane, air-gapped private cloud and beta edge build all run the same engine
- ✓Hybrid search, quantization and reranking are native rather than add-ons, so one system covers dense, sparse and multi-vector retrieval
- ✓Strong enterprise adoption signal — Canva, HubSpot, Roche, Bosch, OpenTable and Deutsche Telekom are named users — plus SOC 2, HIPAA and GDPR alignment with SSO/SAML and RBAC
- ✓$50M Series B in March 2026 (total $87.8M) gives multi-year runway in a market consolidating around larger platforms
Cons
- ✗Operational overhead of a second stateful service: separate deployment, storage, snapshots, health endpoint, gRPC surface and failure modes to coordinate with your primary database
- ✗Splitting documents from vectors introduces a dual-write consistency problem — a failed write leaves either an unembedded document or an orphaned vector, so you need retry logic, a dead-letter queue or a reconciliation job
- ✗Below roughly 5 million vectors the performance case is weak: independent comparison puts pgvector at 5-50ms and Qdrant at 5-30ms on comparable datasets, which rarely justifies new infrastructure
- ✗No published list price for the production Standard tier — hourly resource-based billing makes forecasting harder than a per-seat quote, and Premium gates SSO and private VPC links behind a minimum spend
- ✗Independent review coverage is thin: G2 and similar sites carry few reviews and block automated retrieval, so there is little third-party evidence of support quality at enterprise scale
- ✗Analysts note the market is drifting toward integrated vector capabilities inside existing data platforms (Databricks, Snowflake, Oracle, the hyperscalers), which pressures standalone vector databases
Pricing
Free
$0
- ✓Single-node cluster
- ✓0.5 vCPU, 1GB RAM, 4GB disk
- ✓Free cloud inference on selected models
- ✓For prototypes and testing
Standard
Usage-based
- ✓Dedicated resources with flexible scaling
- ✓High-availability setups
- ✓Backup and disaster recovery
- ✓99.5% uptime SLA
Premium
Contact for pricing
- ✓Minimum spend commitment
- ✓SSO
- ✓Private VPC links
- ✓Multi-AZ topology
- ✓Custom encryption keys
- ✓99.9% uptime SLA
- ✓24/7 support
Hybrid Cloud / Private Cloud
Contact for pricing
- ✓Data plane in customer infrastructure
- ✓Air-gapped deployment
- ✓Kubernetes-based
- ✓Migration services
The engine itself is Apache-2.0 and free to self-host, so the only licence cost is Qdrant Cloud. Cloud billing is metered hourly on actual resource consumption — vCPU, memory, storage, backup storage and paid inference tokens — rather than per seat, and Qdrant does not publish a dollar figure for the Standard tier; you size a cluster and pay for what it consumes. A free forever tier gives a single 0.5 vCPU / 1GB node for prototypes. Premium requires a minimum spend and is where SSO, private VPC links, multi-AZ topology, customer-managed encryption keys, the 99.9% SLA and 24/7 support live. Hybrid Cloud and Private Cloud are sales-quoted. Practical budgeting note: memory is the dominant cost driver in vector search, which is why the quantization features are a pricing feature as much as a performance one.
Security & Compliance
Connect
Sources
This page was written from 7 sources, 4 on domains other than qdrant.tech.
Stay Ahead of the Curve
Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.
SubscribeRelated Products
Tacnode Context Lake
PostgreSQL-compatible context lake giving AI agents shared, live, transactional state at decision time
Reducto
Agentic document parsing API that turns complex PDFs, scans and spreadsheets into citation-grounded data for AI, now with the 1¢-per-page r-1 model
Euno
AI-native context platform that gives enterprise agents governed, trustworthy data
Prevalent AI
A sovereign enterprise knowledge graph that gives security teams and AI agents context