Small business▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
2%from 0% in September 2026
Inside the floor by 9 pointsRank 12 → 7 of 59
Azure · 2 categories · RankedAzure Cosmos DB
78Judge labels
5First choices
12Negative labels
14 / 14Models named it
2Categories
October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10.8, every buyer segment counted.
Best standing
7% in NoSQL for enterprise buyers
Rank 12 of 73 in the mid-market standingaccepted challenger
0 of 14 models made it the first choice on the direct prompt; 20% of its 20 labels there were negative.
What the models named instead of Azure Cosmos DB →By buyer segmentRead the same way at every buyer size.
Small business7 of 60
2%11 labels
criticized challenger
Mid-market12 of 73
0%20 labels
accepted challenger
Enterprise3 of 54
7%40 labels
accepted challenger
In nosql · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading
Standing by category
Every category where a model named Azure Cosmos DB for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.
| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| NoSQL databases | Data platform | 0% | 12 of 73 | 20% | 20 | accepted challenger | ▼−4Since September 2026: 4% → 0%, −4 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Managed relational databases | Data platform | 0% | 62 of 82 | 100% | 1 | under 10 labels · led by Amazon RDS at 45% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
Movement
Since September 2026, Azure Cosmos DB held within the floor in all two categories: no change cleared 11 points.
Best category · NoSQL · by segment
Mid-market▼−4Since September 2026: 4% → 0%, −4 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
0%from 4% in September 2026
Inside the floor by 7 pointsRank 5 → 12 of 69
Enterprise▲+4Since September 2026: 4% → 9%, +4 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
9%from 4% in September 2026
Inside the floor by 7 pointsRank 3 → 4 of 53
All categories · Mid-market
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| NoSQL | 4% | 0% | ▼−4Since September 2026: 4% → 0%, −4 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 5 → 12 of 73 |
| Managed databases | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 57 → 62 of 82 |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
By model
How each model treated Azure Cosmos DB across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.ShowHide
By model
How each model treated Azure Cosmos DB across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.
ShowHide| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 1 | 2 |
| Perplexity Sonar | 0 | 3 | 0 | 0 | 3 |
| Grok 4.20 | 0 | 0 | 0 | 1 | 1 |
| Mistral Small | 0 | 1 | 0 | 0 | 1 |
| DeepSeek V4 Flash | 0 | 3 | 0 | 1 | 4 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 0 | 2 | 0 | 2 |
| Kimi K2 | 0 | 0 | 1 | 1 | 2 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 2 | 0 | 1 | 3 |
By framing
Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.
FramingLabels by classFirst choices
Direct15 labels1
Paraphrase14 labelsNone
Comparative18 labels1not counted in share
Budget-constrained7 labels2
Scale-constrained12 labels2
Negative12 labels1not counted in share
First choiceAlternativeMentionNegative78 labels in all, every segment counted; 5 of the 7 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.
What the models said for it
Verbatim evidence the judge attached to positive labels.
“For a managed cloud option, Azure Cosmos DB, Amazon DynamoDB, or Google Cloud Firestore are all common consumption-based choices.” Perplexity Sonar · NoSQL · paraphrase prompt · alternative
“Prefer managed services to keep ops headcount low: MongoDB Atlas, Amazon DynamoDB, Azure Cosmos DB, Couchbase Capella, managed Cassandra.” Muse Glimmer 30B · NoSQL · scale prompt · alternative
“If your B2B company is built on Azure, Azure Cosmos DB (Table API or NoSQL API) is the direct equivalent to DynamoDB” Gemini 3.5 Flash · NoSQL · paraphrase prompt · alternative
“Cons: Pricing complexity (RU/s billing model can be confusing), best if you're already on Azure” DeepSeek V4 Flash · NoSQL · paraphrase prompt · alternative
And against it
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Proprietary database engines (Aurora, Cosmos DB, Spanner) - highest lock-in risk” Kimi K2 · Managed databases · negative prompt · soft negative
“Solid but heavier management overhead; ~$2,000/month typical” DeepSeek V4 Flash · NoSQL · direct prompt · soft negative
“Azure Cosmos DB's trust comes from vendor lock-in acceptance” Muse Glimmer 30B · NoSQL · negative prompt · soft negative
“They are built with highly specialized, proprietary APIs.” Gemini 3.5 Flash · NoSQL · negative prompt · soft negative
Named alongside
The products named in the same answers as Azure Cosmos DB, over the 78 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Azure Cosmos DB was named but was not.ShowHide
Named alongside
The products named in the same answers as Azure Cosmos DB, over the 78 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Azure Cosmos DB was named but was not.
ShowHideProductSame answerTook the first choice insteadHead to head
A head-to-head page exists where both products are among a category's top eight. The other rows are the same fact without a page behind them, so they link to the product instead.
What carried it into the answer
The sites and pages cited by the answers that named Azure Cosmos DB. A fact about retrieval, not a lever on the model.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 66 of the 78 answers that named Azure Cosmos DB and are not a share of its labels.
Domains cited
guideflow.com29
peerspot.com26
thectoclub.com26
aerospike.com24
mongodb.com20
windowsforum.com19
couchbase.com17
dnsstuff.com17
infoworld.com17
g2.com15
210 of the 210 domain citations in answers naming Azure Cosmos DB came from somebody else's page.
Pages cited
Pages are listed as the models cited them.
Search and answers
Where Azure Cosmos DB stands in Google search beside where it stands in the models' answers.ShowHide
Search and answers
Where Azure Cosmos DB stands in Google search beside where it stands in the models' answers.
ShowHideIn search
Google, US estimates- Searches for its name, Google
- 1,900 a month (“azure cosmos db”)
- AI search demand for its name, est.
- 108 a month
- Its own site
- It sits on Azure's site (azure.cn), so there are no site figures for it alone
In answers
This editionShare of first choices
0%
rank 12 of 73 in nosql
Segment leader
74%
MongoDB
- First choices
- 5 across its categories
- Named in
- 78 answers
- Its own site cited
- in 66 of the answers that named it
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
Names read as Azure Cosmos DB
What the judge wrote, as written, with how often. The vendor table decides that these count as Azure Cosmos DB; a claim can dispute any of them.
Microsoft Azure Cosmos DB 5Cosmos DB 4Google Cloud Firestore/Cosmos DB 1
Follow Azure Cosmos DB
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
The company
Azure is the company behind Azure Cosmos DB.ShowHide
The company
Azure is the company behind Azure Cosmos DB.
ShowHideOn record
Company records- Also from Azure
- Azure ACR, Azure AD Conditional Access, Azure AD Graph API, Azure AI Document Intelligence, Azure AI Foundry, Azure AI Gateway, Azure AI Search, Azure API Management and 79 more
Is this your product?
Claim this page
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Azure Cosmos DB's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Azure Cosmos DB, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
What a new claim receivesHide what a new claim receives
A new claim receives the current edition's vendor brief for Azure Cosmos DB by email, built from the raw record of the edition. It shows:
- where Azure Cosmos DB is named, by buyer and by framing, and which cells hold its first choices;
- the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
- its vocabulary against the segment leader's, and the pages the models cited;
- who was chosen in the answers that did not name Azure Cosmos DB, and every reason the record gives;
- a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
- one page of published figures cleared to show a buyer.