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

"It's very easy to set up and runs easily."
"The solution's most valuable feature is its documentation, which allows new users to easily learn, deploy, and use it."
"The user interface of Microsoft Azure Cosmos DB is the best part of the entire Microsoft ecosystem; I find it to be the best user interface you can ever hope for, especially when compared to AWS and GCP, which do not measure up as well."
"Microsoft Azure Cosmos DB is easy to use and implement for application programmers."
"I would recommend Cosmos. It made our lives a lot easier. There's not a big learning curve in order to understand the structure and how to use it."
"The most valuable features of Microsoft Azure Cosmos DB were the general infrastructure, ease to use, and interface."
"Their new feature, dynamic data masking, is very cool and useful for us."
"The features most valuable to us in Microsoft Azure Cosmos DB are the auto scale and change feed. These features allow us to do some operations that are not possible with SQL Server."
"Latency and availability are incredible."
"The value that it has added to my AI or search workloads is that I think it's optimized that process and made it easier; we have a lot of unstructured data coming from different dissimilar systems and different data sources, so correlating those things together and making sense of it has been very beneficial."
 

Cons

"The hybrid algorithm needs improvement."
"I think Chroma doesn't have a ready-made containerized image available."
"If you want to bring the data from AWS, you must pay data egress costs. That's a pain point."
"New features can be included and its stability can be further improved."
"It would be nice to have more options to ingest the data, for example, more file options or more search options."
"We are at the beginning of production, and everything is working very well. The price can always be lower, but currently, it's not a problem."
"One of our biggest pain points is the backup and restore functionality needs improvement."
"One area for improvement is the ease of writing SQL queries and stored procedures in Microsoft Azure Cosmos DB. Writing an SQL query and a stored procedure on top of that is a little challenging."
"A further simple application is required for Brazil."
"In the long run, there should be an addition of more features, especially because this space is evolving quickly. It all boils down to how many more features you are adding, how many integrations you are supporting, and how many more APIs you have that are standard APIs."
 

Pricing and Cost Advice

"The current version is an open-source."
"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."
"Cost isn’t a big hurdle for us right now. The solution is not costly."
"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."
"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's licensing costs are monthly."
"Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high."
"The RU's use case determines our license fees."
"Cosmos DB is a managed offering, so its cost is understandably higher."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
892,776 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
9%
Government
8%
Financial Services Firm
12%
Legal Firm
12%
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,776 professionals have used our research since 2012.