Loading…
Loading…
Customer outcome · anonymized
A ~60-person, engineering-heavy company ran Kiro — AWS’s agentic IDE, billed per developer by tier — across about 45 developers. Most had been put on a tier by guesswork. DevSpend reconciled each developer’s actual monthly credit usage against the tier they held and recommended the cheapest tier that still covered their real usage. Acting on those recommendations cut the Kiro bill by roughly half — on the order of $1,000+ a month — with no developer losing access.
The outcome
The savings came entirely from moving each developer to the most efficient tier for their usage — not from cutting anyone off.
Kiro developers
~45
Billed per developer, by tier, through AWS
Kiro bill reclaimed
~50%
After right-sizing every developer
Monthly savings
~$1,000+
Recurring, with no loss of access
Developers who lost access
None
Everyone kept a tier that fits their usage
How it worked
DevSpend keeps billing, entitlements, and activity separate, then reconciles them — so the recommended tier is grounded in what each developer actually used, not a flat policy.
Billing — what AWS actually charged
Kiro is billed per developer through AWS, so its spend hides inside the broader AWS invoice. DevSpend broke it out per developer and per tier.
Entitlements — the tier each developer held
Every developer sat on a tier — Pro, Pro+, Pro Max, or Power — usually assigned by guesswork rather than measured need.
Activity — the credits each developer used
Per-developer monthly credit consumption showed who was comfortably inside a cheaper tier and who was paying overage that an upgrade would undercut.
What right-sizing looks like
Examples of the moves the recommendations surface, using Kiro's published list prices — Pro $20, Pro+ $40, Pro Max $100, Power $200. Illustrative, not the customer's individual data.
| From | To | Monthly change | Why |
|---|---|---|---|
| Power · $200 | Pro Max · $100 | −$100/mo | Monthly credit usage sat well inside the Pro Max allowance. |
| Pro Max · $100 | Pro+ · $40 | −$60/mo | A power tier assigned by default to a moderate user. |
| Pro+ · $40 | Pro · $20 | −$20/mo | Light, occasional usage well under the Pro+ allowance. |
| Pro · $20 + overage | Pro+ · $40 | Net saving | Recurring $0.04/credit overage cost more than the next tier up. |
Kiro credits do not roll over, so any allowance bought above real monthly usage is pure waste — which is why matching the tier to actual usage recovers so much.