Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams building retrieval and semantic-search backends that need payload filtering alongside vector similarity, for developers who want a self-hosted retrieval layer with first-party clients in their existing language, and for edge/offline applications that need the same query surface in-process instead of over the network.
Where this stands now
qdrant/qdrant ranks #9 of 76 tracked AI Infrastructure items by composite score (8.6 against a section median of 8.1). The section currently carries 41 Gold, 33 Silver, 2 Bronze. RepoRadar has retained observations for this record since 2026-08-28 (43 days in the current window). Signal extremes versus the section: momentum at the 80th percentile; novelty at the 1th percentile.
Who should use it
Who should skip it
Skip qdrant/qdrant if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
qdrant/qdrant is tracked by RepoRadar as a developer tool in the AI Infrastructure section. First seen 2026-08-28; the source record was last checked on 2026-08-28. The current verdict is 'try now' with a Gold tier and easy setup difficulty. qdrant/qdrant leads on workflow potential (9.7) and maturity (9.2); its lowest signal is novelty (5.0), so factor that in before investing setup time. This page summarizes the evidence RepoRadar captured from https://github.com/qdrant/qdrant.
How this item is evaluated
The qdrant/qdrant record combines a 8.6/10 composite score with separate popularity (100.0), risk (conditional), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The README explicitly warns that the documented quick-start Docker command starts an insecure deployment without authentication, open to all network interfaces. Anyone running it beyond localhost owns the auth and network boundary before data goes in; Self-hosted stateful service: you own persistence, snapshots, upgrade path, and capacity planning between releases; The project also sells a managed cloud offering, so evaluate which features you are relying on are in the Apache-2.0 repository versus the hosted tier.