| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Workflow orchestration | Data platform | 0% | 18 of 79 | 22% | 18 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Orchestration | 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 → 18 of 79 |
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 | 1 | 1 | 3 |
| 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.20 | 0 | 1 | 1 | 0 | 2 |
| Mistral Small | 0 | 0 | 1 | 0 | 1 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 0 | 1 |
| Llama 4 Maverick | 0 | 0 | 2 | 0 | 2 |
| Qwen 3.7 Flash | 0 | 0 | 2 | 0 | 2 |
| Kimi K2 | 0 | 0 | 0 | 1 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 1 | 1 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 1 | 0 | 1 | 2 |
| Muse Glimmer 30B | 0 | 1 | 0 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“Teams already deep in one cloud should lean on that cloud's native option, AWS Step Functions” Claude Haiku 4.5 · Orchestration · comparative prompt · alternative
“Winner: AWS Step Functions or Google Cloud Workflows ... 100% serverless” Gemini 3.5 Flash · Orchestration · budget prompt · alternative
“Event-driven microservices | Temporal or AWS Step Functions” DeepSeek V4 Flash · Orchestration · negative prompt · alternative
“Workflows mostly connecting AWS services: Step Functions” GPT-6 Luna · Orchestration · 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.
“High vendor lock-in — JSON-based state machines, difficult to migrate.” Kimi K2 · Orchestration · negative prompt · hard negative
“if you need cloud portability or haven't checked limits and pricing... It ties workflows to AWS” GPT-6 Luna · Orchestration · negative prompt · soft negative
“workflows built on these platforms are difficult to migrate if cloud strategy changes” Claude Haiku 4.5 · Orchestration · negative prompt · soft negative
“Deep integration with AWS, but limited if you’re not AWS-heavy.” GLM 4.7 FlashX · Orchestration · scale 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 39 of the 46 answers that named AWS Step Functions and are not a share of its labels.
111 of the 111 domain citations in answers naming AWS Step Functions 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 Step Functions's own pages state, read September 28, 2026: aws.amazon.com/step-functions, aws.amazon.com/step-functions/sla, aws.amazon.com/step-functions/faqs, aws.amazon.com/step-functions/details, aws.amazon.com/step-functions/pricing. 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 Step Functions'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 Step Functions, 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 Step Functions by email, built from the raw record of the edition. It shows: