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.

Weaviate appears to have several advantages over Milvus, particularly in maturity, licensing and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Milvus leads in popularity with 45,634 stars vs 16,729 stars for Weaviate. The 173% higher star count indicates stronger community adoption. In terms of developer contributions, Milvus has 4,179 forks, indicating strong developer engagement.
Milvus and Weaviate are moving at much the same rate, adding 396 stars and adding 130 stars respectively over the last 30 days (+0.9% vs +0.8%). Neither is pulling away from the other on momentum alone.
Both projects show recent activity, with Milvus last updated 6 hours ago and Weaviate 2 hours 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.
Weaviate provides self-hosting options for complete data control and customization, while Milvus may be primarily cloud-based or require different deployment approaches.

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