AWS blames bug for Kiro pricing glitch that drained developer limits
Briefly

AWS limited Kiro usage in July after a surge of developers signing up to try the IDE, with the spike driven largely by pricing changes and throttling problems at rival IDEs such as Cursor and Claude Code. AWS retracted earlier pricing tier details and had initially proposed three interaction-based tiers: a free cap of 50 agentic interactions, Pro at $19 for 1,000 interactions, and Pro+ at $39 for 3,000 interactions. AWS then revised pricing to quota vibe and spec requests instead, offering free, Pro ($20), Pro+ ($40), and Power ($200) tiers with specified vibe and spec limits.
In July, AWS had to limit the usage of Kiro, just days after announcing it in public preview, due to the sheer number of developers flocking to try out the IDE, mainly driven by pricing changes and throttling issues in rival IDEs, such as Cursor and Claude Code. It had also retracted details of the pricing tiers it planned for the service.
However, last week, it introduced a revised pricing structure moving away from simple interactions to vibe and spec requests: free with a cap of 50 vibe and 0 spec requests; Pro at $20 with 225 vibe and 125 spec requests, Pro+ at $40 with 450 vibe and 250 spec requests; and Power at $200 for 2,250 vibe and 1,250 spec requests.
Read at InfoWorld
[
|
]