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

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
9th
Average Rating
8.8
Reviews Sentiment
4.9
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2026, in the Vector Databases category, the mindshare of Microsoft Azure Cosmos DB is 6.2%, up from 2.9% compared to the previous year. The mindshare of Supabase Vector is 7.4%, up from 5.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%
Supabase Vector7.4%
Other86.4%
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.
Ankit_Yadav - PeerSpot reviewer
Software Developer at a performing arts with 1-10 employees
Building full web apps without managing my own backend has become simple and cost effective
I think the support system can be better because after Supabase Vector stopped working in India, there is no support. Nobody knows how to deal with the database now. The naming structure is a little difficult. If you are naming a table, the guidance is sometimes not clear. It's a very simple feature to add sometimes but the process is very difficult. When I'm in Supabase Vector, there is a feature where I have to create a table. At the start, for newcomers, it's difficult, and then it becomes hard. You have to look for the documentation and YouTube videos to understand how it works. Supabase Vector stopped working in India due to some government guidelines, so I have to switch with something else now.

Quotes from Members

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

Pros

"The solution is scalable, and we intend to increase our usage."
"I would recommend Microsoft Azure Cosmos DB to other users without hesitation."
"Cosmos DB is a document database that stores data in JSON format for faster retrieval of unstructured data. I personally appreciate the speed, which is significantly better for unstructured data, especially since Cosmos DB had JSON as a data type early on."
"The most valuable features of Microsoft Azure Cosmos DB include the TTL, the ability to scale up and down as needed, and geo-replication, which comes out of the box."
"The fact that scalability can be achieved by simply configuring availability zones is very attractive."
"The customer gave us the feedback that they are able to easily find the data they are looking for. It is very quick."
"Azure Cosmos DB offers numerous data connectors that provide a platform for seamless integration with various platforms and visualization tools such as Power BI. It allows connection via multiple data connectors to integrate data in any desired format."
"The feature I have found most valuable in Microsoft Azure Cosmos DB is its scalability and speed."
"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."
"Supabase enables us to lower the skill floor while keeping the ceiling high."
"Supabase Vector rapidly increases the speed and efficiency with which I search through a database, helping with my data analysis tasks."
"Supabase Vector is easy to set up and cost-effective because the alternative is Firebase, which requires a credit card."
 

Cons

"In Microsoft manufacturing, managers really need to know about the product."
"New features can be included and its stability can be further improved."
"An improvement would be a more robust functionality around updating elements on a document, or some type of procedural updates that don't require pulling the entire document."
"There are some disadvantages as it is costly compared to other NoSQL databases."
"I have to say technical support is not very good as it takes too long. Sometimes it can take them two or three days to respond to your ticket."
"It is not as easy to use as DynamoDB."
"Azure Cosmos DB could be better for business intelligence and analytical queries."
"The built-in integration of the solution is tight."
"I notice that the schema visualizer can be improved. Additionally, the internal AI assistant powered by GPT can also be improved."
"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."
"I think the support system can be better because after Supabase Vector stopped working in India, there is no support."
 

Pricing and Cost Advice

"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."
"Everything could always be cheaper. I like that Cosmos DB allows us to auto-scale instead of pre-provisioning a certain capacity. It automatically scales to the demand, so we only pay for what we consume."
"Its pricing is not bad. It is good."
"For the cloud, we don't pay for the license, but for the on-prem versions, we do pay."
"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."
"With heavy use, like a large-scale IoT implementation, you could easily hit a quarter of a million dollars a month in Azure charges if Cosmos DB is a big part of it."
"Microsoft provides fair pricing."
"Cosmos DB is a highly cost-optimized solution when used correctly."
"The solution's cost is reasonable compared to other solutions."
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
12%
Legal Firm
11%
Comms Service Provider
9%
Manufacturing Company
8%
Comms Service Provider
14%
Manufacturing Company
7%
Outsourcing Company
7%
Financial Services Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise22
Large Enterprise58
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise2
 

Questions from the Community

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...
What needs improvement with Supabase Vector?
I think the support system can be better because after Supabase Vector stopped working in India, there is no support. Nobody knows how to deal with the database now. The naming structure is a littl...
What is your primary use case for Supabase Vector?
I'm using Supabase Vector for the Postgres part. I use their Postgres database as the main requirement for the product from my side. If I am building a small website or any product, I don't need to...
 

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: April 2026.
892,776 professionals have used our research since 2012.