AWS has introduced new pricing for Kiro, its AI-driven coding tool, but unlike the pricing originally announced, the latest plans are "a wallet-wrecking tragedy," according to many of its users.

"Kiro's spec-driven AI IDE is a gem," said open source PHP and Laravel engineer Antonio Ribeiro [1]on GitHub , "until I saw your new pricing."

AWS introduced Kiro last month as a fork of Code OSS (also used by Visual Studio Code) with a distinctive approach to AI coding assistance, based on specifications and tasks.

[2]

"Coming soon" pricing was shown from the start, and looked reasonable, as we [3]reported in our initial hands-on. There were three plans, with free offering 50 interactions per month, Pro at $19.00 per user/month with 1,000 interactions, and Pro+ at $39.00 with 3,000 interactions. Additional interactions were to be $0.04 each.

[4]

[5]

Kiro proved immediately popular. A waitlist was introduced and the pricing [6]disappeared . Last week, new pricing was announced, and to nobody's surprise it is less generous.

AWS now defines two types of Kiro AI request. Spec requests are those started from tasks, while vibe requests are general chat responses. Executing a sub-task consumes at least one spec request plus a vibe request for "coordination," according to an [7]explanatory post . AWS has also given itself scope to consume more requests for a task or chat depending on complexity, whereas at the initial launch AWS developer advocate Nathan Peck reassured developers that a single interaction might be one that "potentially runs for 3-5 minutes of Kiro iterating away on writing code."

[8]

The revised pricing has a free tier with 50 vibe requests (yes, no spec requests at all); Pro at $20 with 225 vibe and 125 spec; Pro+ with 450 vibe and 250 spec; and Power at $200 with 2,250 vibe and 1,250 spec. Additional vibe requests are $0.04 each, while spec requests cost five times more, $0.20 each.

[9]Vibe coding tool Cursor's MCP implementation allows persistent code execution

[10]Devs are frustrated with AI coding tools that deliver nearly-right solutions

[11]AWS slaps usage caps on Kiro as AI editor preview proves too popular for its own good

[12]AWS previews Kiro IDE for developers who are over vibe coding

"Let's crunch the numbers," said Ribeiro. For light coding, he uses at least 3,000 spec requests per month, while he hardly uses vibe requests at all. "Vibe requests are useless because the vibe agent constantly nags me to switch to spec requests, claiming my chats are 'too complex'," he reported. He estimated that light coding will cost him around $550 per month and full time coding around $1,950 per month. As an open source developer who builds for the community, "this pricing is a kick in the shins," he said.

Another GitHub issue on the subject [13]complains that the Pro+ allocated monthly limits "were completely consumed within 15 minutes of usage in a single chat session."

Likewise, the Kiro Discord community includes many complaints about the opaque pricing and the surprising number of requests consumed, many more than the documentation suggests. "In practice, when I make one request, Kiro has already consumed four to six vibe requests. It never consumes just one," said one comment.

According to Ribeiro, Kiro's competitors are cheaper by a wide margin, including Amazon Q, which costs $40 for 3,000 requests, Trae, which has unlimited requests (but can be slow), and Windsurf, which is "way more affordable for experimenting."

[14]

We have asked Amazon for comment.

Views vary on the value of AI for developers, but the Kiro pricing issue shows another kind of risk – that costs can [15]escalate unexpectedly . ®

Get our [16]Tech Resources



[1] https://github.com/kirodotdev/Kiro/issues/2182

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aKOidT419fmMafz2_HMV7gAAABY&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://devclass.com/2025/07/15/hands-on-with-kiro-the-aws-preview-of-an-agentic-ai-ide-driven-by-specifications/

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aKOidT419fmMafz2_HMV7gAAABY&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aKOidT419fmMafz2_HMV7gAAABY&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://www.theregister.com/2025/07/21/aws_kiro_usage_cap/

[7] https://kiro.dev/blog/understanding-kiro-pricing-specs-vibes-usage-tracking/

[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aKOidT419fmMafz2_HMV7gAAABY&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[9] https://www.theregister.com/2025/08/05/mcpoison_bug_abuses_cursor_mcp/

[10] https://www.theregister.com/2025/07/29/coders_are_using_ai_tools/

[11] https://www.theregister.com/2025/07/21/aws_kiro_usage_cap/

[12] https://www.theregister.com/2025/07/14/aws_kiro_agentic_ide/

[13] https://github.com/kirodotdev/Kiro/issues/2171

[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/aiml&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aKOidT419fmMafz2_HMV7gAAABY&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[15] https://www.theregister.com/2025/08/15/are_you_willing_to_pay/

[16] https://whitepapers.theregister.com/