| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Source control hosting | Developer platform | 2% | 6 of 33 | 27% | 30 | criticized challenger | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| CI/CD platforms | Developer platform | 0% | 7 of 43 | 5% | 22 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Internal developer portals | Developer platform | 0% | 30 of 52 | 0% | 1 | under 10 labels · led by Port at 53% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Source control | 0% | 2% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 5 → 6 of 33 |
| CI/CD | 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 6 → 7 of 43 |
| Developer portals | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 30 of 52, unchanged |
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
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 6 | 1 | 7 |
| GPT-5.4 mini | 0 | 1 | 2 | 0 | 3 |
| Gemini 3.5 Flash | 0 | 3 | 0 | 1 | 4 |
| Perplexity Sonar | 0 | 1 | 1 | 1 | 3 |
| Grok 4.20 | 0 | 2 | 2 | 1 | 5 |
| Mistral Small | 0 | 1 | 2 | 1 | 4 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 1 | 2 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 2 | 2 | 1 | 5 |
| Kimi K2 | 1 | 3 | 1 | 1 | 6 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 0 | 2 |
| MiniMax M2.5 | 0 | 2 | 3 | 1 | 6 |
| GPT-6 Luna | 0 | 0 | 2 | 0 | 2 |
| Muse Glimmer 30B | 0 | 3 | 1 | 0 | 4 |
Verbatim evidence the judge attached to positive labels.
“Azure DevOps ⭐ Best Overall Value” Kimi K2 · Source control · budget prompt · first choice
“Strong integration with Microsoft ecosystem... Highly Microsoft-centric enterprise environments (though Microsoft is actively pushing much of ADO's innovation toward GitHub).” Gemini 3.5 Flash · Source control · scale prompt · alternative
“Best For: Large enterprises, legacy .NET development shops... Microsoft cloud/corporate ecosystem.” Gemini 3.5 Flash · Source control · comparative prompt · alternative
“Azure DevOps | Microsoft-centric organizations | Tight Azure integration, good for .NET shops” Kimi K2 · CI/CD · scale prompt · alternative
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.
“GitHub, GitLab, Bitbucket, and Azure DevOps have all experienced security breaches, credential leaks, and supply chain attacks” Mistral Small · Source control · negative prompt · soft negative
“Only choose if you're deeply invested in the Microsoft/Azure ecosystem. Otherwise, it's an extra platform to manage.” DeepSeek V4 Flash · CI/CD · paraphrase prompt · soft negative
“Be cautious about closed-source SaaS for sensitive code: GitHub, Bitbucket, Azure DevOps, and AWS CodeCommit” Perplexity Sonar · Source control · negative prompt · soft negative
“Azure DevOps can feel rigid and "corporate" to modern engineering teams, making it less attractive” Gemini 3.5 Flash · Source control · direct prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 138 of the 165 answers that named Azure DevOps and are not a share of its labels.
322 of the 322 domain citations in answers naming Azure DevOps came from somebody else's page.
Pages are listed as the models cited them.
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.
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.
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 DevOps'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 DevOps, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Azure DevOps by email, built from the raw record of the edition. It shows: