Try our new research platform with insights from 80,000+ expert users

Microsoft Azure Cosmos DB vs Supabase Vector 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

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)
Supabase Vector
Ranking in Vector Databases
12th
Average Rating
9.0
Reviews Sentiment
5.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Vector Databases category, the mindshare of Microsoft Azure Cosmos DB is 5.8%, up from 1.3% compared to the previous year. The mindshare of Supabase Vector is 10.4%, up from 2.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Market Share Distribution
ProductMarket Share (%)
Microsoft Azure Cosmos DB5.8%
Supabase Vector10.4%
Other83.8%
Vector Databases
 

Featured Reviews

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.
Kaustubh Sule - PeerSpot reviewer
Co-Founder • Full Stack Developer at Padhakoo
Easy to use, and there is no need to get involved in any tedious deployment process
If you are a business building a social media app, there will be thousands of users for every such app. Each user will have a post or something. When multiple users try to hit the like button on your post or try to comment on your post, each of them would be an API request, and Supabase Vector does not charge for them like. The API requests are kind of unlimited. If you compare Supabase Vector to any of the other services like Firebase, AWS, or Azure, all the tools charge per request. From a scalability standpoint, if you are a small-scale startup and you have around 1,00,000 or 2,00,000 users, then Supabase Vector is a perfect choice for you. I have never heard about any scalability issues in the product. Scalability-wise, I rate the solution a ten of ten.

Quotes from Members

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

Pros

"Microsoft Azure Cosmos DB offers the response times needed for advanced analytics applications."
"Reading and inserting data into Microsoft Azure Cosmos DB is a very smooth process."
"I like the way you can create and delete records. You pass a JSON, and then it creates a record."
"It's not a specific feature that I value, but the scalability of this system is the most impressive aspect."
"What I like about Microsoft Azure Cosmos DB is that it's easy to do data ingestion and use the data in different applications. If you talk about business intelligence such as the Power BI tool, it's easy to connect because both are Microsoft products. With Microsoft Azure Cosmos DB, it's easy to connect and do data ingestion."
"We doubled our productivity with this small application."
"Scaling the workloads is one of the key advantages of Cosmos, preventing the database from becoming a performance bottleneck."
"The solution is stable."
"Supabase enables us to lower the skill floor while keeping the ceiling high."
"Supabase enables us to lower the skill floor while keeping the ceiling high."
"The platform's role-level security feature is quite effective for spatial data management."
"The tool is easy to use."
 

Cons

"In Microsoft Azure Cosmos DB, I would suggest improvements in security."
"We had some performance issues with a data segregation query. We worked closely with Microsoft to solve the problem of performance where, for example, one query had a delay of almost two or three minutes for this one use case. Microsoft tried to improve the product, but in the end, the solution was to change to MongoDB. MongoDB had better performance."
"An improvement could include increasing the document size or providing a method to manage larger sets efficiently. If they want to keep a 2 MB limit, they should provide a way to chain multiple documents in a systematic way so that developers do not have to figure out what to do when a document is larger than 2 MB."
"A better description and more guidance would help because the first time I created it, I didn't understand that a container is similar to a table in SQL."
"Microsoft Azure Cosmos DB's pricing model is complicated, which people don't understand."
"A further simple application is required for Brazil."
"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."
"The one thing that I have been working on with Microsoft with regard to this is the ability to easily split partitions and have it do high-performance cross-partition queries. That is the only place where either our data size or our throughput has grown beyond one partition, so being able to do cross-partition queries efficiently would be my number one request."
"The support for React Native CLI is an area with certain shortcomings where improvements are required."
"I think there are still many Postgres features that can be developed further by the Supabase team."
"I think there are still many Postgres features that can be developed further by the Supabase team."
"One area for the solution improvement is the inclusion of more sample code in various programming languages, particularly PHP."
 

Pricing and Cost Advice

"When we've budgeted for our resources, it's one of the more expensive ones, but it's still not very expensive per month."
"Azure Cosmos DB is generally a costly resource compared to other Azure resources. It comes with a high cost. We have reserved one thousand RUs. Free usage is also limited."
"Microsoft provides fair pricing."
"Cost isn’t a big hurdle for us right now. The solution is not costly."
"Cosmos DB is a managed offering, so its cost is understandably higher."
"It is cost-effective. They offer two pricing models. One is the serverless model and the other one is the vCore model that allows provisioning the resources as necessary. For our pilot projects, we can utilize the serverless model, monitor the usage, and adjust resources as needed."
"Pricing, at times, is not super clear because they use the request unit (RU) model. To manage not just Azure Cosmos DB but what you are receiving for the dollars paid is not easy. It is very abstract. They could do a better job of connecting Azure Cosmos DB with the value or some variation of that."
"Azure Cosmos DB's pricing is competitive, though there is a need for more personalized pricing models to accommodate small applications without incurring high charges. A suggestion is to implement dynamically adjustable pricing that accounts for various user needs."
"The solution's cost is reasonable compared to other solutions."
"As per the product's regular pricing plans, the tools are available to users for 20 to 25 USD per month."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Legal Firm
13%
Financial Services Firm
11%
Comms Service Provider
9%
Manufacturing Company
8%
Comms Service Provider
15%
Computer Software Company
8%
Healthcare Company
6%
Manufacturing Company
6%
 

Company Size

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

Questions from the Community

What do you like most about Microsoft Azure Cosmos DB?
The initial setup is simple and straightforward. You can set up a Cosmos DB in a day, even configuring things like availability zones around the world.
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 needs improvement with Supabase Vector?
I think there are still many Postgres features that can be developed further by the Supabase team.
What is your primary use case for Supabase Vector?
I am exploring Supabase for my project on UMKM.
 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
No data available
 

Overview

 

Sample Customers

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Information Not Available
Find out what your peers are saying about Microsoft Azure Cosmos DB vs. Supabase Vector and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.