{"id":356229,"date":"2025-08-19T07:26:15","date_gmt":"2025-08-19T07:26:15","guid":{"rendered":"https:\/\/www.europesays.com\/uk\/356229\/"},"modified":"2025-08-19T07:26:15","modified_gmt":"2025-08-19T07:26:15","slug":"aws-pricing-for-kiro-dev-tool-a-wallet-wrecking-tragedy-the-register","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/uk\/356229\/","title":{"rendered":"AWS pricing for Kiro dev tool &#8216;a wallet-wrecking tragedy&#8217; \u2022 The Register"},"content":{"rendered":"<p>AWS has introduced new pricing for Kiro, its AI-driven coding tool, but unlike the pricing originally announced, the latest plans are &#8220;a wallet-wrecking tragedy,&#8221; according to many of its users.<\/p>\n<p>&#8220;Kiro&#8217;s spec-driven AI IDE is a gem,&#8221; said open source PHP and Laravel engineer Antonio Ribeiro <a target=\"_blank\" href=\"https:\/\/github.com\/kirodotdev\/Kiro\/issues\/2182\" rel=\"noopener\">on GitHub<\/a>, &#8220;until I saw your new pricing.&#8221;<\/p>\n<p>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.<\/p>\n<p>&#8220;Coming soon&#8221; pricing was shown from the start, and looked reasonable, as we <a target=\"_blank\" href=\"https:\/\/devclass.com\/2025\/07\/15\/hands-on-with-kiro-the-aws-preview-of-an-agentic-ai-ide-driven-by-specifications\/\" rel=\"noopener\">reported<\/a> in our initial hands-on. There were three plans, with free offering 50 interactions per month, Pro at $19.00 per user\/month with\u00a01,000 interactions, and Pro+ at $39.00 with 3,000 interactions. Additional interactions were to be $0.04 each.<\/p>\n<p>Kiro proved immediately popular. A waitlist was introduced and the pricing <a target=\"_blank\" href=\"https:\/\/www.theregister.com\/2025\/07\/21\/aws_kiro_usage_cap\/\" rel=\"noopener\">disappeared<\/a>. Last week, new pricing was announced, and to nobody&#8217;s surprise it is less generous.<\/p>\n<p>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 &#8220;coordination,&#8221; according to an <a target=\"_blank\" href=\"https:\/\/kiro.dev\/blog\/understanding-kiro-pricing-specs-vibes-usage-tracking\/\" rel=\"noopener\">explanatory post<\/a>. 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 &#8220;potentially runs for 3-5 minutes of Kiro iterating away on writing code.&#8221;<\/p>\n<p>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.<\/p>\n<p>&#8220;Let&#8217;s crunch the numbers,&#8221; said Ribeiro. For light coding, he uses at least 3,000 spec requests per month, while he hardly uses vibe requests at all. &#8220;Vibe requests are useless because the vibe agent constantly\u00a0nags me to switch to spec requests, claiming my chats are &#8216;too complex&#8217;,&#8221; 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, &#8220;this pricing is a kick in the shins,&#8221; he said.<\/p>\n<p>Another GitHub issue on the subject <a target=\"_blank\" href=\"https:\/\/github.com\/kirodotdev\/Kiro\/issues\/2171\" rel=\"noopener\">complains<\/a> that the Pro+ allocated monthly limits &#8220;were completely consumed within 15 minutes of usage in a single chat session.&#8221;<\/p>\n<p>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. &#8220;In practice, when I make one request, Kiro has already consumed four to six vibe requests. It never consumes just one,&#8221; said one comment.<\/p>\n<p>According to Ribeiro, Kiro&#8217;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 &#8220;way more affordable for experimenting.&#8221;<\/p>\n<p>We have asked Amazon for comment.<\/p>\n<p>Views vary on the value of AI for developers, but the Kiro pricing issue shows another kind of risk \u2013 that costs can <a target=\"_blank\" href=\"https:\/\/www.theregister.com\/2025\/08\/15\/are_you_willing_to_pay\/\" rel=\"noopener\">escalate unexpectedly<\/a>. \u00ae<\/p>\n","protected":false},"excerpt":{"rendered":"AWS has introduced new pricing for Kiro, its AI-driven coding tool, but unlike the pricing originally announced, the&hellip;\n","protected":false},"author":2,"featured_media":356230,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3163],"tags":[323,1942,53,16,15],"class_list":{"0":"post-356229","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-artificial-intelligence","8":"tag-ai","9":"tag-artificial-intelligence","10":"tag-technology","11":"tag-uk","12":"tag-united-kingdom"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@uk\/115054246782002183","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/356229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/comments?post=356229"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/356229\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media\/356230"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media?parent=356229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/categories?post=356229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/tags?post=356229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}