| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Secrets management | Identity and access | 8% | 4 of 59 | 10% | 60 | accepted challenger | ▲+2Since September 2026: 4% → 6%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Privileged access management | Identity and access | 2% | 11 of 73 | 0% | 5 | under 10 labels · led by Delinea Secret Server at 37% | ▲+2Since September 2026: 0% → 2%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Non-human identity management | Identity and access | 0% | 49 of 128 | 33% | 6 | under 10 labels · led by JumpCloud at 14% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Secrets | 4% | 6% | ▲+2Since September 2026: 4% → 6%, +2 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 5 → 4 of 59 |
| PAM | 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 21 → 11 of 73 |
| NHI management | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 49 of 128, 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 | 4 | 2 | 0 | 6 |
| GPT-5.4 mini | 3 | 3 | 0 | 0 | 6 |
| Gemini 3.5 Flash | 0 | 4 | 3 | 0 | 7 |
| Perplexity Sonar | 0 | 1 | 1 | 1 | 3 |
| Grok 4.20 | 0 | 3 | 0 | 3 | 6 |
| Mistral Small | 1 | 3 | 1 | 0 | 5 |
| DeepSeek V4 Flash | 0 | 3 | 2 | 1 | 6 |
| Llama 4 Maverick | 0 | 1 | 1 | 0 | 2 |
| Qwen 3.7 Flash | 0 | 4 | 1 | 2 | 7 |
| Kimi K2 | 0 | 4 | 0 | 0 | 4 |
| GLM 4.7 FlashX | 0 | 3 | 1 | 0 | 4 |
| MiniMax M2.5 | 0 | 2 | 2 | 1 | 5 |
| GPT-6 Luna | 1 | 2 | 0 | 0 | 3 |
| Muse Glimmer 30B | 1 | 5 | 1 | 0 | 7 |
Verbatim evidence the judge attached to positive labels.
“my default recommendation is: 1) If you're cloud-native and mostly on one major cloud: use the cloud provider's native secrets service. - AWS: AWS Secrets Manager” GPT-5.4 mini · Secrets · paraphrase prompt · first choice
“Best default for most mid-market teams on one major cloud: AWS Secrets Manager if you're mostly on AWS” GPT-5.4 mini · Secrets · direct prompt · first choice
“Already AWS-native and want minimal ops: AWS Secrets Manager is the pragmatic first step.” Muse Glimmer 30B · Secrets · paraphrase prompt · first choice
“Often cited as a cost-accessible option, especially for organizations already using AWS.” Mistral Small · PAM · budget 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.
“GitGuardian cautions that AWS Secrets Manager, GCP Secret Manager, and Azure Key Vault can create fragmentation if you operate in multi-cloud setups.” Perplexity Sonar · Secrets · negative prompt · soft negative
“Proprietary free tiers (e.g., cloud-native like AWS Secrets Manager) work if single-cloud but limit multi-cloud flexibility.” Grok 4.20 · NHI management · budget prompt · soft negative
“AWS Secrets Manager and Azure Key Vault have had vulnerabilities... They may not suit multi-cloud environments” MiniMax M2.5 · Secrets · negative prompt · soft negative
“Strong vendor lock-in—if multi-cloud or hybrid, cross-cloud access adds friction/cost.” Grok 4.20 · Secrets · 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 191 of the 214 answers that named AWS Secrets Manager and are not a share of its labels.
633 of the 633 domain citations in answers naming AWS Secrets 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 AWS Secrets Manager's own pages state, read September 28, 2026: aws.amazon.com/secrets-manager, aws.amazon.com/secrets-manager/sla, aws.amazon.com/secrets-manager/faqs, aws.amazon.com/secrets-manager/pricing, aws.amazon.com/secrets-manager/features. 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 AWS Secrets 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 AWS Secrets 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 AWS Secrets Manager by email, built from the raw record of the edition. It shows: