| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| AI security platforms | Security operations | 0% | 41 of 233 | 0% | 5 | under 10 labels · led by SentinelOne Singularity at 11% | |
| AI governance platforms | Data platform | 0% | 76 of 135 | 0% | 1 | under 10 labels · led by Credo AI at 18% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 0 | 1 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 1 | 0 | 0 | 0 | 1 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 1 | 1 | 0 | 2 |
| GLM 4.7 FlashX | 0 | 2 | 0 | 0 | 2 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“Model scanning (Guardian), AI SBOM (Radar), runtime guardrails (Layer); ... Broadest coverage.” Grok 4.1 Fast · AI security · comparative prompt · first choice
“Best for: Mid‑market companies that want governance tightly coupled with security infrastructure.” GLM 4.7 FlashX · AI governance · direct prompt · alternative
“If your risk is downloading a malicious model from Hugging Face, look at Protect AI.” Gemini 3.5 Flash · AI security · comparative prompt · alternative
“Add model‑centric tools (HiddenLayer, Checkmarx, Protect AI)” GLM 4.7 FlashX · AI security · 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.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 11 of the 12 answers that named Protect AI and are not a share of its labels.
No domain is on file for Protect AI, so its own site is not marked.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 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 Protect AI'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 Protect AI, 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 Protect AI by email, built from the raw record of the edition. It shows: