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
5.8
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2026, in the Vector Databases category, the mindshare of Microsoft Azure Cosmos DB is 5.9%, up from 2.5% compared to the previous year. The mindshare of Supabase Vector is 8.5%, up from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Microsoft Azure Cosmos DB5.9%
Supabase Vector8.5%
Other85.6%
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 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."
"When all resources are at the same point, there is no lag and in production we have experienced minimal issues, with the project live for two years without any database problems."
"Azure Cosmos DB helped improve the quality of our search results."
"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."
"Overall, I would rate Microsoft Azure Cosmos DB a nine out of ten."
"We chose Azure Cosmos DB initially because of the type of data that we needed to store. We have a schema that is very nondeterministic and flexible. It is always changing based on whatever data we need to acquire from different devices, so we needed a document store with a flexible schema."
"The feature I have found most valuable in Microsoft Azure Cosmos DB is its scalability and speed."
"The solution is used because we get faster response times with large data sets than with SQL."
"Supabase Vector is easy to set up and cost-effective because the alternative is Firebase, which requires a credit card."
"The tool is easy to use."
"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 enables us to lower the skill floor while keeping the ceiling high."
 

Cons

"I would like to see Cosmos DB introduce a feature that would convert machine language to human-readable queries."
"We'd like to avoid full DR replication if possible, as this would result in significant cost savings."
"We encountered an issue with Cosmos DB's recently introduced hierarchical partition feature."
"A limitation in Azure Cosmos DB is the 2 MB document size. Developers need more systemic support in chaining multiple documents if more than 2 MB is required."
"Better documentation on how to integrate with other components would be helpful because I was struggling with this."
"At this stage, we would like more enterprise support. We use MongoDB a lot, and we're trying to get rid of MongoDB, so I would like to see more features in the Cosmos DB API for MongoDB space."
"The query searching functionality has some complexities and could be more user-friendly."
"There are no particular factors that need improvement. There is a little bit of a learning curve with scaling workloads, but it works smoothly."
"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."
"The support for React Native CLI is an area with certain shortcomings where improvements are required."
"I think the support system can be better because after Supabase Vector stopped working in India, there is no support."
"I think there are still many Postgres features that can be developed further by the Supabase team."
 

Pricing and Cost Advice

"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."
"The cost is the biggest limitation of this solution."
"Cost isn’t a big hurdle for us right now. The solution is not costly."
"We are not consuming so much yet since we are at the beginning of using this solution. I would rate the pricing of Microsoft Azure Cosmos DB a six out of ten."
"It's expensive. I would rate it a seven out of ten for pricing."
"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."
"Pricing is mid- to high-end."
"I would rate Cosmos DB's cost at seven out of ten, with ten being the highest."
"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.
886,576 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Legal Firm
12%
Financial Services Firm
12%
Comms Service Provider
9%
Manufacturing Company
8%
Comms Service Provider
14%
Computer Software Company
7%
Manufacturing Company
7%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise22
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: February 2026.
886,576 professionals have used our research since 2012.