Learn how Milvus 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
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Both Milvus 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.
Milvus leads in popularity with 45,957 stars vs 16,784 stars for Weaviate. The 174% higher star count indicates stronger community adoption. In terms of developer contributions, Milvus has 4,222 forks, indicating strong developer engagement.
Milvus is growing faster, adding 448 stars in the last 30 days (+1%) against adding 94 stars for Weaviate (+0.6%). Milvus is both larger and pulling further ahead.
Both projects show recent activity, with Milvus last updated 8 hours ago and Weaviate 47 minutes ago.
Both tools share common technology foundations, being built with JavaScript, Bash, Python, Golang, C. However, they differ in their additional technology choices: Milvus uses CSS, Rust, Objective-C, C++.
Weaviate has been in development longer, starting 10 years ago, compared to Milvus which began 7 years ago. This 3.5-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 Milvus's Apache-2.0 license, potentially offering greater flexibility for commercial use and integration.
Both tools serve similar use cases in Vector Databases.
Both Milvus and Weaviate offer self-hosting capabilities, giving you full control over your data and infrastructure.