| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| API gateways | Developer platform | 2% | 11 of 66 | 43% | 7 | under 10 labels · led by Kong Gateway at 53% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| API management | Developer platform | 2% | 10 of 61 | 25% | 20 | criticized challenger | ▼−3Since September 2026: 4% → 2%, −3 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| API management | 4% | 2% | ▼−3Since September 2026: 4% → 2%, −3 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 6 → 10 of 61 |
| API gateways | 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 39 → 11 of 66 |
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 | 1 | 0 | 1 | 0 | 2 |
| GPT-5.4 mini | 0 | 0 | 1 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 2 | 2 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.20 | 0 | 2 | 1 | 2 | 5 |
| Mistral Small | 0 | 0 | 2 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 1 | 3 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 1 | 1 | 2 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 2 | 0 | 1 | 3 |
| MiniMax M2.5 | 1 | 1 | 1 | 1 | 4 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 3 | 0 | 3 |
Verbatim evidence the judge attached to positive labels.
“WSO2 API Manager is the most complete API management platform you can run without paying a license fee” Claude Haiku 4.5 · API management · budget prompt · first choice
“I recommend starting with Tyk Open Source or WSO2 API Manager” MiniMax M2.5 · API gateways · budget prompt · first choice
“Comprehensive feature set, full API lifecycle management... Can be resource-intensive, steeper learning curve” MiniMax M2.5 · API management · budget prompt · alternative
“If you want an open‑source solution with strong protocol support and AI assistance → WSO2 API Manager” GLM 4.7 FlashX · API management · comparative 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.
“CVE-2026-5430 (CVSS 9.8, path traversal/RCE, added to CISA KEV Sep 2026)” Grok 4.20 · API gateways · negative prompt · hard negative
“Status: AVOID UNTIL PATCHED” GLM 4.7 FlashX · API management · negative prompt · hard negative
“WSO2 is one of the few fully open-source enterprise-grade API managers available, but it is incredibly complex.” Gemini 3.5 Flash · API management · negative prompt · soft negative
“WSO2 relies on a heavy proprietary core that can make scaling and containerizing instances difficult” Qwen 3.7 Flash · API gateways · 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 55 of the 58 answers that named WSO2 API Manager and are not a share of its labels.
173 of the 173 domain citations in answers naming WSO2 API Manager 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.
What WSO2 API Manager's own pages state, read September 28, 2026: wso2.com/customers/apogee-goes-beyond-compliance-with-wso2-api-manager, wso2.com/customers/enhancing-asabris-business-operations-with-wso2-api-manager, wso2.com/library/blogs/wso2-api-manager-4-7-release, wso2.com/blogs/thesource/introducing-wso2-api-manager-4-1, wso2.com/blogs/thesource/introducing-wso2-api-manager-4-2. 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 WSO2 API Manager'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 WSO2 API Manager, 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 WSO2 API Manager by email, built from the raw record of the edition. It shows: