AWS Business Continuity
Standing by category
| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Business continuity management | Security operations | 2% | 14 of 114 | 0% | 1 | under 10 labels · led by LogicManager at 24% |
Movement
By model
How each model treated AWS Business Continuity across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.ShowHide
By model
| 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 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 0 | 0 | 0 | 0 |
| 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 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 1 | 0 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
By framing
What the models said for it
Verbatim evidence the judge attached to positive labels.
“Start with ISO 22301 templates combined with Microsoft Azure or AWS cloud services” MiniMax M2.5 · Business continuity · budget prompt · first choice
And against it
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.
Named alongside
The products named in the same answers as AWS Business Continuity, over the 1 answer that named it. Took the first choice instead counts the answers where the other product was the first choice and AWS Business Continuity was named but was not.ShowHide
Named alongside
What carried it into the answer
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 1 of the 1 answers that named AWS Business Continuity and are not a share of its labels.
Domains cited
No domain is on file for AWS Business Continuity, so its own site is not marked.
Pages cited
Pages are listed as the models cited them.
Follow AWS Business Continuity
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.
Claim this page
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 Business Continuity'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 Business Continuity, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
What a new claim receivesHide what a new claim receives
A new claim receives the current edition's vendor brief for AWS Business Continuity by email, built from the raw record of the edition. It shows:
- where AWS Business Continuity is named, by buyer and by framing, and which cells hold its first choices;
- the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
- its vocabulary against the segment leader's, and the pages the models cited;
- who was chosen in the answers that did not name AWS Business Continuity, and every reason the record gives;
- a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
- one page of published figures cleared to show a buyer.