Learn how Chroma and Qdrant 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
Repository

Both Chroma and Qdrant 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.
Both tools have similar popularity levels, with Chroma having 29,086 stars and Qdrant having 34,062 stars on GitHub. In terms of developer contributions, Qdrant has 2,590 forks, indicating strong developer engagement.
Qdrant is growing faster, adding 629 stars in the last 30 days (+1.9%) against adding 250 stars for Chroma (+0.9%). Qdrant is both larger and pulling further ahead.
Both projects show recent activity, with Chroma last updated 8 hours ago and Qdrant 10 hours ago.
Both tools share common technology foundations, being built with JavaScript, Bash, Python, Rust. However, they differ in their additional technology choices: Chroma uses CSS, Typescript, JSX, Next.js, Golang while Qdrant leverages C, Objective-C.
Qdrant has been in development longer, starting 6 years ago, compared to Chroma which began 4 years ago. This 2.4-year head start suggests Qdrant may have more mature features and established processes.
Both projects use the Apache-2.0 license, providing identical terms for usage and distribution.
Both tools serve similar use cases in Vector Databases.
Chroma provides self-hosting options for complete data control and customization, while Qdrant may be primarily cloud-based or require different deployment approaches.