In short: Two Amazon engineers replaced Claude Sonnet 4.6 with Strands Decider, a small open-source "decision model", for labeling tickets into 20 categories, and report the same quality at about 98% lower cost and a 78% shorter call. The trick is not that a small model is smarter; it is that ticket labeling is a closed choice from a known list, so a model that only picks options (and says how sure it is) is enough. This playbook explains when that swap makes sense for your own workload, how to test it without risk, and where the math stops working.
What a decision model is, in one paragraph
Strands Decider, published by the Strands Agents team under the Apache-2.0 license, is not a chatbot. According to its docs, it "answers typed questions about a state instead of generating text." You give it some text (the state, for example a ticket) and one or more questions, each of a fixed type:
- noul: a yes-or-no question, returned as the probability that the answer is true.
- choice: pick one option from a set, returned as the selected option, every option's probability and a confidence.
- score: rate something on an ordered scale, returned as an expected score, the distribution and a confidence.
Under the hood, the team takes a pre-trained LLM torso, removes the part that writes text, and adds a small "pointer head" (just over a million parameters, per the launch post) that scores each option. The upside is speed, a single-token-sized output and a calibrated confidence number. The downside, which the launch post states plainly, is that it is much worse than reasoning models at complex problems and cannot do coding, chat or summarization at all.
What Amazon actually changed
The case study on the Strands blog (November 9, 2026) describes an internal ticketing system where Sonnet 4.6 ran a long system prompt on every ticket and produced JSON with reasoning, choosing among 20 labels. The tickets ranged from customer escalations and capacity requests to automated alarms and security findings.
They first tried the original 2B Decider, then switched to the Gemma 4 based E4B build because it did clearly better on their test tickets, and tuned how confident the model had to be before a label was applied. The reported numbers:
- Average time per call: 4,215 ms for Sonnet 4.6 vs 897 ms for Decider E4B (78% less).
- Tokens per ticket: 6,724 vs 2,010 (70% less). Output fell from 170 tokens to 1, because the model returns a choice, not JSON.
- Cost per million tickets: about $22,200 vs about $500, at published us-east-1 on-demand prices.
The serving setup was ordinary AWS: tickets land in SQS, a Lambda function reads them and calls a SageMaker real-time endpoint running Decider E4B on ml.g5.xlarge (one A10G GPU, 24 GB). The model used about 19 GiB and a single request took about 640 ms. You can see the measured and cost tables from the case study in the official screenshots at the end of this post.
Two details most summaries skip
- The prompt had to shrink. The E4B model is trained and served at a 4,096-token window, and Amazon's existing label descriptions alone were longer than that. They rewrote each of the 20 labels as a one- or two-sentence criterion, added a "none" option, and on long tickets dropped the oldest comments. Part of the token saving comes from that rewrite, not from the model.
- JSON key order changed the answer. Sending the same content with keys in a different order moved the output probabilities by up to 0.19. They now sort keys on every request. If you compare runs, do the same.
The cost math, redone for smaller teams
Amazon's $500 per million tickets assumes enough traffic to keep GPU instances busy. Most teams do not have that. I reran the numbers using only the figures in the case study and Anthropic's published price list, to show where the swap starts to pay off.
- Sonnet 4.6 per ticket: 6,554 input tokens at $3 per million plus 170 output tokens at $15 per million comes to $0.0222, which matches the case study.
- Decider at full use: at about 640 ms per request, one instance handles roughly 5,600 tickets an hour. $1.408 per hour divided by 5,600 is about $0.00025 per ticket, or $250 per million. Amazon keeps headroom for bursts, which is why its real figure is about $500.
- One instance left on all month: 730 hours at $1.408 is $1,027.84. Divide that by Sonnet's $0.0222 and the break-even point is roughly 46,300 tickets a month. Below that, a single always-on GPU endpoint costs more than just calling Sonnet.
So the headline "98% cheaper" is a high-volume result. At a few thousand decisions a month, the cheaper move may be a smaller LLM, prompt caching for the repeated system prompt, or running the 2B Decider on a machine you already own. My own cost table is the last image at the end of this post.
Options compared
| Option | Price basis | Cost per 1M tickets* | Speed (as published) | Good fit |
|---|---|---|---|---|
| Claude Sonnet 4.6 (what Amazon replaced) | $3 input / $15 output per 1M tokens | ~$22,200 | 4,215 ms average call (case study) | Labels that need an explanation, catalogs that change often, long context |
| Claude Haiku 4.5 (cheaper LLM, my estimate) | $1 input / $5 output per 1M tokens | ~$7,400 at the same token counts | Not measured in the case study | Teams that want a cheaper LLM without new infrastructure |
| Strands Decider E4B on SageMaker ml.g5.xlarge | $1.408 per instance-hour | ~$250 at full use, ~$500 with headroom | 897 ms average call; ~640 ms per request on the instance | High-volume closed-choice decisions, latency-sensitive paths |
| Strands Decider 2B on your own GPU or Mac | Open weights, no per-call fee (your hardware and power) | Depends on your hardware | ~115 ms median on an RTX 3090; ~153 ms on an M3 MacBook for small tasks (launch post) | Experiments, internal tools, gating agent tool calls |
*Sonnet and Haiku rows use the case study's 6,554 input and 170 output tokens per ticket. The Haiku row is my arithmetic, not a measured run; a real Haiku setup could need a different prompt.
Is your workload a decider job? A five-question check
The case study's own "lessons" section gives the conditions. I turned them into a checklist you can run against a real task:
- Is the output a fixed list? Labels, queues, teams, yes/no, or a 1-5 score. If you need free text back, stop here.
- Does the list stay stable? Amazon warns that a catalog that changes weekly is a bad fit.
- Does the useful context fit in a few thousand tokens? The Gemma 4 builds are trained at 4,096 tokens. If you need whole documents, a decider probably cannot replace the LLM.
- Is the volume high enough? Use the break-even math above with your own token counts and instance price.
- Does latency matter? If a person or another system waits on the decision, a sub-second answer is worth more than if the job runs overnight.
Three or more "yes" answers make a pilot worthwhile. Good candidates the Strands team lists include routing a request to a model, tool, team or queue; checking tool arguments, grounding or policy; and scoring model responses during evaluation.
How to test the pattern on your own data
Step 1: ask one question locally
The docs show the quickest start: install the package from PyPI and point it at the published 2B model.
pip install strands-decider
strands-decider ask StrandsAgents/strands-decider-2B-qwen3.5-v1-2610 \
--state "Help! My payouts have been failing for 3 days." \
--choice "Which team should handle this?=billing,technical,sales"
Pass --device cuda, mps or cpu explicitly; otherwise the CLI picks CUDA, then MPS, then CPU. The Gemma 4 models (E2B, E4B, 12B, 26B-A4B) need the code from the GitHub main branch, because the PyPI package does not include Gemma 4 support yet: pip install "strands-decider @ git+https://github.com/strands-labs/strands-decider".
Step 2: rewrite your labels as short criteria
Copy Amazon's move: one or two sentences per label, plus an explicit "none" option. The HTTP API accepts a description for each option under criteria, so the label name stays short and the criterion carries the meaning.
Step 3: serve it and send a few hundred real items
strands-decider serve <model> --port 8000 exposes POST /v1/systemone plus /health. Note the docs' warning: the server binds to 127.0.0.1, has no authentication, and its behavior under concurrent requests is not verified, so treat it as a local experiment until you put it behind your own gateway. For hosting, the repo's deploy/ folder includes a SageMaker guide, and the server also answers on /ping and /invocations, the paths SageMaker calls.
Step 4: run both models side by side
This is the part Amazon says it would copy regardless of model. Their Lambda read a three-way switch from AWS AppConfig on every message: BEDROCK (LLM only), DUAL (both run, the LLM's answer is applied, the two are compared) and DECIDER (decider only). Running DUAL on real traffic and judging every disagreement told them more than offline evals, and rolling back was a 45-second config change. You can build the same switch with any feature-flag tool; an offline version is simply logging both answers to a table. If you already use a prompt test suite, see my Promptfoo tutorial for a quick way to score the disagreements.
Step 5: set confidence bands before you switch
The architecture docs suggest a starting convention: at 0.9 confidence or above, act without a check; from 0.5 to 0.9, confirm first; below 0.5, send it to a person. They also say the right thresholds depend on what each action costs when wrong, and should be measured on your own traffic. In the docs' own recorded example, "failing payouts" was routed to technical at 0.622 confidence, which lands in the confirm band, exactly the kind of borderline case a human or an LLM fallback should see.
Editor's note
Who it's for: teams already paying for a frontier LLM to classify, route or gate things at high volume, with a stable label set; agent builders who want a cheap check before a tool call runs.
Who it's not for: anyone who needs explanations, summaries or generated replies; low-volume workflows where one always-on GPU costs more than the LLM calls; label sets that change every week.
Gotchas I found in the docs:
- Gemma 4 model ids not working after
pip install strands-decider: the PyPI release lacks Gemma 4 support; install from the GitHub main branch. - HTTP 422 on long inputs: a prompt longer than the checkpoint's window is refused, with a message naming the window. Trim old comments or shorten label criteria.
- Out-of-memory on a busy GPU: without
--max-concurrency, up to 40 requests can run at once, and a burst of large ones can exhaust GPU memory. Set a small value. - Health checks failing at startup: the server warms up before accepting requests and
/healthfails until it finishes, so allow for it in startup timeouts. - Unstable results between runs: sort JSON keys in structured states; Amazon saw probabilities move by up to 0.19 from key order alone.
Where this fits with the rest of your stack
A decider does not replace your LLM layer; it sits in front of it. A common shape is decider first, LLM only when confidence is low. If you route between several providers, a proxy like the one in my LiteLLM tutorial keeps the LLM fallback simple, and tracing with Langfuse shows which calls were expensive enough to be worth moving. If you plan to host the model yourself, GPU hourly prices vary a lot by provider; my Modal vs Runpod vs Lambda comparison covers that side.
FAQ
Is Strands Decider free to use?
The code is released under the Apache-2.0 license and the weights are published on Hugging Face (the StrandsAgents organization, with the five v1 models also mirrored under the amazon organization). There is no per-call fee from the project; you pay for whatever hardware or cloud instance runs it.
Which Decider size should I start with?
The README's guidance: the 12B and 26B-A4B are the most accurate, the 26B-A4B is better calibrated but needs about twice the memory and latency of the 12B, the E4B suits a GPU shared with other work, and the E2B fits tight memory or CPU. For a first local test, the 2B Qwen3.5 model is the documented quickstart. Amazon picked E4B after it beat the 2B on their own tickets.
Can a decider handle my chatbot or support replies?
No. It only picks options, answers yes/no or returns a score. It can decide which team or template a reply should use, but an LLM (or a person) still has to write the text.
If your LLM bill is mostly spent picking from a list, a one-week DUAL run on real traffic will tell you more than any benchmark.
Last verified: 2026-11-13. Images: screenshots of the Strands Agents blog case study, the Strands Decider docs and the strands-decider GitHub README, plus one table made by lightmind24 (see the official screenshots at the end of this post).
lightmind24 is an independent review site, not affiliated with Amazon Web Services, Strands Agents or Anthropic.
Sources: Strands blog: Amazon replaces Sonnet 4.6 with Strands Decider · Introducing Strands Decider · Decider overview · Decider inference docs · Decider architecture · strands-decider on GitHub · Claude API pricing
댓글
댓글 쓰기