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

"Cosmos is preferred because of its speed, robustness, and utilization. We have all the merchandising information in Cosmos DB, which provides concrete and optimized data when searching for new products on the site. It is faster than other relational databases."
"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."
"The peace of mind that Microsoft Azure Cosmos DB provides regarding global distribution is invaluable."
"Microsoft Azure Cosmos DB is fast, and its performance is good compared to normal SQL DB."
"The ability to scale automatically is very valuable."
"The connectors, such as the MongoDB connector and the integration with SQL, are incredibly valuable."
"The customer gave us the feedback that they are able to easily find the data they are looking for. It is very quick."
"The dynamic autoscale or serverless model of Microsoft Azure Cosmos DB has indeed helped reduce our costs and operational effort by allowing us to scale horizontally in a straightforward manner according to our needs."
"Supabase enables us to lower the skill floor while keeping the ceiling high."
"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."
 

Cons

"There are multiple approaches to implementing multitenant architecture on Azure Cosmos DB, but there is still no single or best-recommended approach when you have a big variance in the size of your tenants. That is something that still needs to be worked on."
"The price can always be lower, but currently, it's not a problem."
"The API compatibility has room for improvement, particularly integration with MongoDB. You have to connect to a specific flavor of MongoDB. We'd also like a richer query capability in line with the latest Mongo features. That is one thing on our wish list. The current version is good enough for our use case, but it could be improved."
"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."
"The query is a little complex. SQL server should have more options. But the query should be better."
"In Microsoft Azure Cosmos DB, I would suggest improvements in security."
"One of our biggest pain points is the backup and restore functionality needs improvement."
"The only area Microsoft Azure Cosmos DB can improve on is its documentation; while it is solid and very useful, enhancements in the indexing documentation would help users save costs and make it more cost-effective."
"I think there are still many Postgres features that can be developed further by the Supabase team."
"I think the support system can be better because after Supabase Vector stopped working in India, there is no support."
"One area for the solution improvement is the inclusion of more sample code in various programming languages, particularly PHP."
"I think there are still many Postgres features that can be developed further by the Supabase team."
"The support for React Native CLI is an area with certain shortcomings where improvements are required."
 

Pricing and Cost Advice

"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."
"Cosmos DB is cost-effective when starting but requires careful management."
"Cosmos DB gave us three accounts for $400. We pay according to the usage."
"Right now, I have opted for the student subscription plan, for which Microsoft charges me around 100 USD. The pricing of the solution depends on the solution's usage."
"Microsoft Azure Cosmos DB's licensing costs are monthly."
"Its cost is transparent. Pricing depends on the transaction and data size, but overall, it is cheaper compared to hosting it on your corporate network due to other factors like power consumption."
"The solution is very expensive."
"The pricing and licensing model was initially difficult to understand, but as soon as I learned what was going on and how it was priced, it was pretty easy."
"As per the product's regular pricing plans, the tools are available to users for 20 to 25 USD per month."
"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.
887,041 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Legal Firm
11%
Financial Services 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
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.
887,041 professionals have used our research since 2012.