| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Infrastructure as code | Cloud and infrastructure | 4% | 3 of 59 | 24% | 38 | accepted challenger | ▲+5Since September 2026: 0% → 5%, +5 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Network monitoring and management | Network and edge | 0% | 16 of 78 | 0% | 4 | under 10 labels · led by Auvik at 26% | |
| Patch management | IT operations and endpoint | 0% | 63 of 85 | 100% | 1 | under 10 labels · led by ManageEngine Patch Manager Plus at 29% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Workflow orchestration | Data platform | 0% | 46 of 79 | 0% | 1 | under 10 labels · led by Prefect at 21% | newNew since September 2026: not ranked then, 0% now. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| IaC | 0% | 5% | ▲+5Since September 2026: 0% → 5%, +5 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 6 → 3 of 59 |
| Network monitoring | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 16 of 78, unchanged |
| Patching | 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 61 → 63 of 85 |
| Orchestration | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 46 of 79, 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 | 1 | 2 | 0 | 3 |
| GPT-5.4 mini | 0 | 0 | 0 | 1 | 1 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 1 | 2 |
| Perplexity Sonar | 1 | 0 | 0 | 2 | 3 |
| Grok 4.20 | 0 | 3 | 0 | 3 | 6 |
| Mistral Small | 0 | 2 | 0 | 0 | 2 |
| DeepSeek V4 Flash | 1 | 2 | 0 | 1 | 4 |
| Llama 4 Maverick | 1 | 1 | 2 | 0 | 4 |
| Qwen 3.7 Flash | 1 | 2 | 1 | 0 | 4 |
| Kimi K2 | 0 | 3 | 0 | 1 | 4 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 1 | 3 |
| MiniMax M2.5 | 0 | 3 | 1 | 0 | 4 |
| GPT-6 Luna | 0 | 1 | 1 | 0 | 2 |
| Muse Glimmer 30B | 0 | 2 | 0 | 0 | 2 |
Verbatim evidence the judge attached to positive labels.
“If you value simplicity and ease of hiring: Avoid Chef/Puppet; choose Ansible or Terraform.” Qwen 3.7 Flash · IaC · negative prompt · first choice
“the best default choice is usually Ansible or Terraform/OpenTofu” Perplexity Sonar · IaC · budget prompt · first choice
“is OpenTofu or Ansible, as they are suitable for budget-conscious teams” Llama 4 Maverick · IaC · budget prompt · first choice
“✅ Configuration management: Ansible” DeepSeek V4 Flash · IaC · negative prompt · first choice
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.
“If someone suggests using Ansible as your primary IaC tool for cloud provisioning, that's a mistake” DeepSeek V4 Flash · IaC · direct prompt · hard negative
“Use Ansible/Chef/Puppet carefully when the job is configuration management rather than infrastructure provisioning” Perplexity Sonar · IaC · negative prompt · soft negative
“Choose Ansible for configuration and operational automation rather than infrastructure provisioning.” Perplexity Sonar · IaC · comparative prompt · soft negative
“it is best used for post-provisioning configuration, not for managing cloud-native infrastructure state” Gemini 3.5 Flash · IaC · negative 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 121 of the 135 answers that named Ansible and are not a share of its labels.
413 of the 413 domain citations in answers naming Ansible 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.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Conference or event | 1 | undated |
As the event pages on ansible.com state them, read September 28, 2026.
Every page ansible.com exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 29, 2026.
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.
What Ansible's own pages state, read September 28, 2026: ansible.com. A claimed page can correct any of them.
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 Ansible'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 Ansible, 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 Ansible by email, built from the raw record of the edition. It shows:
Ansible is among the products AI models recommend first in Infrastructure as code this edition. Each badge says so in the buyer's words, names the edition, and links to the standing. The next edition issues a new badge; this one stays true as a record of October 2026.
Badges read on light and dark pages. Alt text carries the claim, the category, the edition and the index, so it stays a citation where the image does not load.