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
14th
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 June 2026, in the Vector Databases category, the mindshare of Chroma is 6.7%, down from 12.5% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 6.2%, up from 3.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Microsoft Azure Cosmos DB6.2%
Chroma6.7%
Other87.1%
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."
"Microsoft Azure Cosmos DB is very easy to use."
"Microsoft Azure Cosmos DB offers exceptional stability, boasting a reliability rating of 99.95 percent."
"As a NoSQL database, it offers schema flexibility which simplifies design and reduces initial engineering overhead."
"Cosmos DB's greatest strengths are its easy setup and affordability, especially for those who understand its usage."
"Azure Cosmos DB's resiliency is valuable. It is available in every Azure region, allowing quick information storage and retrieval. We can partition it to improve indexing, enabling us to retrieve information and recreate website content quickly."
"The solution's read capacity and write access functions are very fast so users don't have to wait when fetching or displaying data on a screen."
"Overall, I think Microsoft Azure Cosmos DB works fine; I don't remember any case where our developers or our clients have been disappointed with it."
"The solution is stable."
 

Cons

"The hybrid algorithm needs improvement."
"I think Chroma doesn't have a ready-made containerized image available."
"The main area of improvement is the cost, as the expense is high. Also, when writing processes into Cosmos, sometimes the threshold is met, which can be a problem if developers have not written the code properly, limiting calls to five thousand."
"We had to go to forums to check if it was failing for everyone else. It was surprising that a large organization like Microsoft doesn't provide an official statement about the maintenance or issues that could impact our overall usage."
"Better documentation on how to integrate with other components would be helpful because I was struggling with this."
"Better documentation on how to integrate with other components would be helpful because I was struggling with this."
"Overall, it works very well and fits the purpose regardless of the target application. However, by default, there is a threshold to accommodate bulk or large requests. You have to monitor the Request Units. If you need more data for a particular query, you need to increase the Request Units."
"Overall, it is a good resource. I am not aware of the background, but it seems to currently support only JSON documents."
"The size of the continuation token in Azure Cosmos DB should be static rather than increasing with more data, as it can lead to application crashes. They should use a static key size."
"Areas of improvement for Microsoft Azure Cosmos DB include indexing. While it makes data retrieval easier, it also increases costs."
 

Pricing and Cost Advice

"The current version is an open-source."
"It is cost-efficient as long as you understand the right setup to optimize usage. Knowing the data needs of the organization and adjusting the Microsoft Azure Cosmos DB usage accordingly helps save costs, but if you don't know, you could end up spending more than necessary."
"Microsoft Azure Cosmos DB pricing is based on RUs. Reading 1 KB document costs one RU, whereas writing one document costs five RUs. Pricing for querying depends on the complexity of the query. If you increase the document size, it will automatically increase the RU cost."
"Most customers like the flexibility of the pricing model, and it has not been an issue. They can start small, and the cost grows with adoption, allowing efficient management of the budget. Its pricing model has not been a concern at all for any of our customers. They understand it. It is simple enough to understand. Oftentimes, it is hard to forecast the RUs, but, in general, it has been fine."
"The pricing for Microsoft Azure Cosmos DB is good. Initially, it seemed like an expensive way to manage a NoSQL data store, but so many improvements that have been made to the platform have made it cost-effective."
"Pricing is one of the solution's main features because it is based on usage, scales automatically, and is not too costly."
"Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated."
"Its price is in the middle, neither too low nor too high."
"Its pricing structure is quite flexible."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
896,563 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
10%
Government
8%
Financial Services Firm
12%
Legal 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 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 advice do you have for others considering Chroma?
The solution is very easy to use. Overall, I rate the solution a nine out of ten.
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.
896,563 professionals have used our research since 2012.