Learn how Qdrant and Weaviate differ in their key features, development activity, technology stack and community adoption, so you can decide which of these vector databases is best for you.
Last 30 days
Last commit
9 hours agoRepository age
6 yearsVersion
v1.20.0License
Apache-2.0Self-hosted
YesRepository
qdrant/qdrant
Last 30 days
Last commit
9 hours agoRepository age
11 yearsVersion
v1.40.3License
BSD-3-ClauseSelf-hosted
YesRepository
weaviate/weaviate
Both Qdrant and Weaviate have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Qdrant leads in popularity with 35,389 stars vs 16,934 stars for Weaviate. The 109% higher star count indicates stronger community adoption. In terms of developer contributions, Qdrant has 2,793 forks, indicating strong developer engagement.
Qdrant is growing faster, adding 471 stars in the last 30 days (+1.3%) against adding 72 stars for Weaviate (+0.4%). Qdrant is both larger and pulling further ahead.
Both projects show recent activity, with Qdrant last updated 9 hours ago and Weaviate 9 hours ago.
Both tools share common technology foundations, being built with JavaScript, Bash, Python, C. However, they differ in their additional technology choices: Qdrant uses Rust, Objective-C while Weaviate leverages Golang.
Weaviate has been in development longer, starting 11 years ago, compared to Qdrant which began 6 years ago. This 4.2-year head start suggests Weaviate may have more mature features and established processes.
Weaviate uses the BSD-3-Clause license, which is more permissive than Qdrant's Apache-2.0 license, potentially offering greater flexibility for commercial use and integration.
Both tools serve similar use cases in Vector Databases.
Both Qdrant and Weaviate offer self-hosting capabilities, giving you full control over your data and infrastructure.