Skip to main content
Qdrant−40 Negative

GILD Review

GILD's call and the buying facts behind it.

From GILD research

Should we adopt Qdrant?

When does a team need Qdrant as its own vector database, and what does running it cost in work?

  1. 30-Second TakePick Qdrant if your retrieval needs its own store and leans on metadata filters.
  2. Best fitAI and platform teams whose retrieval needs a dedicated store with selective metadata filters, run on Kubernetes or bought as Qdrant Cloud.GILD Review
  3. Consider another workflowIf your application data already lives in Postgres, pgvector avoids syncing a second store, which practitioners describe as a pain. If the app should run no server at all, an embedded store fits, and Qdrant's own embedded option, Qdrant Edge, is in beta.GILD Review

Drawn from 72 sources and 4 operator insights

GILD analysis

Qdrant Review

Qdrant gives a team a dedicated vector database with payload filtering, hybrid search and quantization, self-hosted under Apache 2.0 or on Qdrant Cloud with a free single node and usage-based Standard billing. Practitioners praise low upkeep and fast filtered search, and report memory and disk sizing, upgrade regressions and cluster recovery as the work that remains. Adopt it when retrieval needs its own store, with payload indexes, headroom and staged upgrades planned up front.

  • Vector Databases
  • AI Costs

The decision

Best fit
AI and platform teams whose retrieval needs a dedicated store with selective metadata filters, run on Kubernetes or bought as Qdrant Cloud.
Consider another workflow
If your application data already lives in Postgres, pgvector avoids syncing a second store, which practitioners describe as a pain. If the app should run no server at all, an embedded store fits, and Qdrant's own embedded option, Qdrant Edge, is in beta.
Adoption condition
Payload indexes on every filtered field before ingestion, memory and disk headroom, and upgrades staged through each minor release with a test run, plus Premium if you need single sign-on.

Basis: Qdrant's pricing page, documentation, security page and Cloud service agreement stored on November 1, 2026, three named deployment accounts (Malt, Zylon and NCSA's Center for AI Innovation), and 48 public accounts from people running Qdrant. Not a GILD performance benchmark.

Buying & deployment factsWhat a team building on it should verify before production traffic grows.
How you buy it

Free, then usage-based

Apache 2.0 when self-hosted. Cloud Standard is usage-based, and Premium is a committed spend.

Source 1, Qdrant, Pricing: PricingSource 2, Qdrant, README: READMESource 6, Qdrant, Premium tier: Premium tierSource 5, Qdrant, Pricing and payments: Pricing and paymentsSource 3, raw.githubusercontent.com, LICENSE: LICENSE

Details

Self-hosted Qdrant is licensed under the Apache License, Version 2.0, a no-charge, royalty-free license. Qdrant Cloud's Free Tier is free forever: one 0.5 vCPU, 1 GB RAM, 4 GB disk node, no credit card needed. Standard is usage-based, paid by credit card or an AWS, GCP or Azure Marketplace subscription. Premium is a committed-usage plan with a minimum spend agreed with Qdrant. Hybrid Cloud is part of the Enterprise plan, and Hybrid and Private Cloud start by contacting Qdrant.

Cost drivers

Billed hourly

Compute, memory, storage, backups and paid inference tokens after the monthly free allowance.

Source 1, Qdrant, Pricing: PricingSource 12, Qdrant, Cloud Inference: Cloud InferenceSource 5, Qdrant, Pricing and payments: Pricing and paymentsSource 2, Qdrant, README: README

Details

Qdrant Cloud Standard has usage-based pricing. Billing follows actual resource usage of compute (vCPU), memory (GB), cluster storage (GB), backup storage (GB) and used inference tokens of paid models, and usage is billed hourly. Cloud Inference is billed per token at a fixed, region-independent price that depends on the model, shown in the Cloud Console. On paid clusters, paid models run on metered tokens after a monthly free allowance of up to 5 million tokens per model.

Where it runs

Self-hosted or Cloud

Self-hosted needs block storage and does not work with NFS or S3. Cloud runs on AWS, GCP and Azure.

Source 20, Qdrant, Installation: InstallationSource 21, Qdrant, Managed Cloud: Managed CloudSource 4, Qdrant, Create a cluster: Create a clusterSource 5, Qdrant, Pricing and payments: Pricing and paymentsSource 22, Qdrant, Security: Security

Details

Qdrant runs self-hosted on 64-bit x86_64 or ARM64 systems and needs block-level storage with a POSIX-compatible file system. It does not work with NFS or S3. Qdrant Managed Cloud runs natively on AWS, GCP and Azure. On Qdrant Cloud, data in Qdrant clusters is stored only in the cluster's deployment region, and telemetry and logs are pushed to Qdrant's US management plane.

What to verify

SSO on Premium

Console sign-in only. Audit logs cover paid clusters from v1.17.0, and logs go to Qdrant's US plane.

Source 6, Qdrant, Premium tier: Premium tierSource 15, Qdrant, Cloud account setup: Cloud account setupSource 23, qdrant.tech, Configure a cluster: Configure a clusterSource 22, Qdrant, Security: Security

Details

Enterprise SSO needs the Premium tier and covers Cloud Console sign-in only. The security page calls SSO a Premium add-on, and the Premium docs list it as included. Audit logs are available for paid clusters from Qdrant v1.17.0. On Qdrant Cloud, telemetry and logs are pushed to Qdrant's US management plane. Unused free clusters are suspended after 1 week and deleted after 4 weeks of inactivity if not reactivated. Under section 10(1) of the Cloud Service Agreement, Qdrant may "use, copy, extract, modify, distribute, analyze, compile, and display" Aggregated Data, usage statistics that do not identify the customer, "for routine business purposes", including developing and improving Qdrant products and services, and may "share versions of" it.

Sourced from Qdrant documentation