No more typing reviews! Try our Samantha, our new voice AI agent.

Chroma vs Microsoft Azure Cosmos DB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 25, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Chroma
Ranking in Vector Databases
11th
Average Rating
8.6
Reviews Sentiment
5.6
Number of Reviews
2
Ranking in other categories
No ranking in other categories
Microsoft Azure Cosmos DB
Ranking in Vector Databases
1st
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
109
Ranking in other categories
Database as a Service (DBaaS) (4th), NoSQL Databases (2nd), Managed NoSQL Databases (1st)
 

Mindshare comparison

As of May 2026, in the Vector Databases category, the mindshare of Chroma is 7.1%, down from 13.0% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 6.2%, up from 2.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Microsoft Azure Cosmos DB6.2%
Chroma7.1%
Other86.7%
Vector Databases
 

Featured Reviews

GagandeepSingh1 - PeerSpot reviewer
Data Science Manager at Zykrr
A simple and easy to use solution that can run on a two-course CPU
We collect customer's feedback, and then we present it to the clients It's very easy to set up and runs easily. It doesn't require great hardware and can run on a two-course CPU with four gigs. The hybrid algorithm needs improvement. I have been using Chroma for one year.  I had some trouble…
reviewer2724105 - PeerSpot reviewer
Senior Director of Product Management at a tech vendor with 1,001-5,000 employees
Provides super sharp latency, excellent availability, and the ability to effectively manage costs across different tenants
For integrating Microsoft Azure Cosmos DB with other Azure products or other products, there are a couple of challenges with the current system. Right now, the vectors are stored as floating-point numbers within the NoSQL document, which makes them inefficiently large. This leads to increased storage space requirements, and searching through a vast number of documents in the vector database becomes quite costly in terms of RUs. While the integration works well, the expense associated with it is relatively high. I would really like to see a reduction in costs for their vector search, as it is currently on the expensive side. The areas for improvement in Microsoft Azure Cosmos DB are vector pricing and vector indexing patterns, which are unintuitive and not well described. I would also like to see the parameters of Fleet Spaces made more powerful, as currently, it's somewhat lightweight. I believe they've made those changes intentionally to better understand the cost model. However, we would like to take a more aggressive approach in using it. One of the most frustrating aspects of Microsoft Azure Cosmos DB right now is that you can only store one vector per document. Additionally, you must specify the configuration of that vector when you create an instance of Microsoft Azure Cosmos DB. Once the database is set up, you can't change the vector configuration, which is incredibly limiting for experimentation. You want the ability to try different settings and see how they perform, as there are numerous use cases for storing more than one vector in a document. While interoperability within the vector database is acceptable—for example, I can search for vectors—I still desire a richer set of configuration options.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it."
"It's very easy to set up and runs easily."
"The best feature about Microsoft Azure Cosmos DB is its interface, which is awesome for accessing data."
"Microsoft Azure Cosmos DB is easy to use and implement for application programmers."
"The product has a lot of useful features that are there and ready to use, it's also very easy to use."
"It's not a specific feature that I value, but the scalability of this system is the most impressive aspect."
"The availability and latency of Azure Cosmos DB are excellent."
"Microsoft Azure Cosmos DB is a Microsoft solution specifically, but we can develop with different developer kits for different databases."
"For modern applications, I would recommend Microsoft Azure Cosmos DB."
"Specifically, we are using the MongoDB API, so we leverage it in that way. I like the flexibility that it offers. My team does not have to spend time building out database tables. We can get going fairly quickly with being able to read and write data into a MongoDB collection that is hosted inside Azure Cosmos DB."
 

Cons

"The hybrid algorithm needs improvement."
"I think Chroma doesn't have a ready-made containerized image available."
"The biggest problem is the learning curve and other database services like RDS."
"There's a little bit of a learning curve because I was new to Azure. But once you learn the tool, it's pretty straightforward."
"The integration of the on-premise solution with the cloud can be difficult sometimes."
"Azure Cosmos DB for NoSQL has a less developed interface and fewer SQL commands than MongoDB, and its community support is also smaller."
"The customer service is lacking. We have a premier support agreement, but support is hit and miss."
"We should have more freedom to tweak it and make our own queries for non-traditional use-cases."
"Cosmos DB should continue evolving in AI features. We expect Cosmos DB to lead on that. There is potential for improved security features, which is important for data storage, especially for Dell Technologies. We must ensure data security remains the top priority."
"The cost is a concern. Microsoft Azure Cosmos DB did not decrease our total cost of ownership. From the standpoint of the old way of doing DBA operations, it did, but our cloud cost increased significantly."
 

Pricing and Cost Advice

"The current version is an open-source."
"It seems to have helped significantly. We were using a different database system previously, and one of the reasons for acquiring Microsoft Azure Cosmos DB was cost."
"Its price is very good for the basic stuff. When you go to a more complicated use case, especially when you need replication and availability zones, it gets a little costly."
"It is expensive. The moment you have high availability options and they are mixed with the type of multitenant architecture you use, the pricing is on the higher end."
"You need to understand exactly the details of how the pricing works technically to stay within reasonable pricing."
"Cosmos DB gave us three accounts for $400. We pay according to the usage."
"Cosmos DB is expensive compared to any virtual machine based on conventional RDBMS like MySQL or PostgreSQL."
"Its pricing structure is quite flexible."
"Its price is in the middle, neither too low nor too high."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
892,611 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
11%
Manufacturing Company
9%
Government
8%
Legal Firm
11%
Financial Services Firm
11%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise22
Large Enterprise58
 

Questions from the Community

What do you like most about Chroma?
The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it.
What needs improvement with Chroma?
The hybrid algorithm needs improvement.
What is your primary use case for Chroma?
We collect customer's feedback, and then we present it to the clients.
What is your experience regarding pricing and costs for Microsoft Azure Cosmos DB?
Microsoft Azure Cosmos DB's pricing model has aligned with my budget expectations because I can tune the RU as I need to, which helps a lot. Microsoft Azure Cosmos DB's dynamic auto-scale or server...
What needs improvement with Microsoft Azure Cosmos DB?
I have not utilized Microsoft Azure Cosmos DB multi-model support for handling diverse data types. I'm not in the position to decide if clients will use Microsoft Azure Cosmos DB or any other datab...
What is your primary use case for Microsoft Azure Cosmos DB?
We have a very large team of developers who develop a solution for our customers. In the part where they need some infrastructure on Microsoft Azure, we deploy entire environments of different type...
 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

1. Google 2. Netflix 3. Amazon 4. Facebook 5. Microsoft 6. Apple 7. Twitter 8. Spotify 9. Adobe 10. Uber 11. Airbnb 12. LinkedIn 13. Pinterest 14. Snapchat 15. Dropbox 16. Salesforce 17. IBM 18. Intel 19. Oracle 20. Cisco 21. HP 22. Dell 23. Samsung 24. Sony 25. LG 26. Panasonic 27. Philips 28. Toshiba 29. Nokia 30. Motorola 31. Xiaomi 32. Huawei
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Chroma vs. Microsoft Azure Cosmos DB and other solutions. Updated: April 2026.
892,611 professionals have used our research since 2012.