<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[takaki-hashnode]]></title><description><![CDATA[takaki-hashnode]]></description><link>https://tech.frommiddle.com</link><generator>RSS for Node</generator><lastBuildDate>Thu, 16 Apr 2026 11:10:10 GMT</lastBuildDate><atom:link href="https://tech.frommiddle.com/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Looked Into Kiro’s New Pricing Plan and Found My Welcome Bonus Quietly Used Up]]></title><description><![CDATA[Overview
Just as I was about to start using kiro in earnest, I came across a post on X by SimSta2 hinting at a possible change to the pricing plan.Since I’m cautious about unexpected charges, I decided to investigate right away.

Relevant post: https...]]></description><link>https://tech.frommiddle.com/looked-into-kiros-new-pricing-plan-and-found-my-welcome-bonus-quietly-used-up</link><guid isPermaLink="true">https://tech.frommiddle.com/looked-into-kiros-new-pricing-plan-and-found-my-welcome-bonus-quietly-used-up</guid><category><![CDATA[AWS]]></category><category><![CDATA[Kiro]]></category><dc:creator><![CDATA[Kentaro Takaki]]></dc:creator><pubDate>Sat, 16 Aug 2025 00:48:05 GMT</pubDate><content:encoded><![CDATA[<h1 id="heading-overview">Overview</h1>
<p>Just as I was about to start using <strong>kiro</strong> in earnest, I came across a post on X by <a target="_blank" href="http://x.com/shimagaji2">SimSta2</a> hinting at a possible change to the pricing plan.<br />Since I’m cautious about unexpected charges, I decided to investigate right away.</p>
<ul>
<li><p>Relevant post: <a target="_blank" href="https://x.com/shimagaji2/status/1956495182020722854">https://x.com/shimagaji2/status/1956495182020722854</a></p>
</li>
<li><p>Official announcement: <a target="_blank" href="https://kiro.dev/blog/pricing-plans-are-live/">Pricing plans are live</a></p>
</li>
</ul>
<h1 id="heading-tldr">TL;DR</h1>
<ul>
<li><p><strong>Who’s affected by the new pricing plan</strong><br />  Users without a Q Developer subscription (logging in via Google / GitHub / AWS BuilderID) are subject to the new plan.<br />  Monthly allowance: <strong>Vibe 50 requests / Spec 0 requests</strong>.<br />  For the first 14 days after the new pricing starts, all users receive a <strong>Welcome Bonus</strong> of Spec 100 and Vibe 100 requests.</p>
</li>
<li><p><strong>How to check your usage</strong><br />  Requires Kiro v0.2.13 or higher. Check from the profile menu in the top-right corner of the editor.<br />  Shows your allowance and consumption.<br />  You can upgrade to a paid plan from <em>Upgrade Plan</em>, but all plans have <strong>pay-per-use</strong> charges if you exceed your limit.</p>
</li>
<li><p><strong>Effect of logging in with a Q Developer Pro ID</strong><br />  When logging in with an IAM Identity Center ID that has Q Developer Pro, the Kiro Plan allowance display disappears, meaning you’re (probably) excluded from the new plan’s restrictions.</p>
</li>
<li><p><strong>Session retention</strong><br />  Switching accounts doesn’t end your IDE-side Kiro sessions — they remain intact.</p>
</li>
<li><p><strong>Caution</strong><br />  Once you use up your free allowance, you’ll automatically switch to pay-per-use billing. Heavy users should be especially careful.</p>
</li>
</ul>
<h1 id="heading-details">Details</h1>
<h2 id="heading-who-is-affected">Who is affected</h2>
<p>If you don’t have a Q Developer subscription, you’re moved to the new pricing model.<br />Logging in via Google / GitHub / AWS BuilderID makes you eligible.<br />(In my case, I logged in with a GitHub account and a WaitList code, so I’m in this group.)</p>
<ul>
<li><p>Monthly allowance: <strong>Vibe 50 / Spec 0</strong></p>
</li>
<li><p>Welcome Bonus (first 14 days after pricing change): <strong>Spec 100 / Vibe 100</strong></p>
</li>
</ul>
<h2 id="heading-how-to-check-your-usage">How to check your usage</h2>
<ul>
<li><p><strong>Required version</strong>: Kiro v0.2.13 or later (check via <em>Help → About</em>)</p>
<p>  <img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755304950263/0058941b-b383-447f-a0cd-0401713f5fba.png" alt class="image--center mx-auto" /></p>
</li>
<li><p><strong>Steps</strong></p>
<ol>
<li><p>Click the profile icon at the right side of the editor.</p>
<p> <img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755304996033/c62f23d4-1d67-4fcb-be61-37927ea582d8.png" alt class="image--center mx-auto" /></p>
</li>
</ol>
</li>
</ul>
<ol start="2">
<li><p>You can monitor your usage.<br /> (In my case, I’m on the free plan, and my Vibe usage was already over halfway…)</p>
<p> <img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755305024793/9fca8f81-a246-4cbf-abf2-0d0ae7849113.png" alt class="image--center mx-auto" /></p>
</li>
</ol>
<ul>
<li><p><strong>Changing plans</strong><br />  You can choose a paid plan from <em>Upgrade Plan</em>.<br />  However, <strong>all plans have pay-per-use charges</strong> for exceeding the request limit.</p>
<p>  <img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755305034182/8e222bb1-8a5b-410d-88e4-cea4689efc54.png" alt class="image--center mx-auto" /></p>
</li>
</ul>
<h2 id="heading-logging-in-with-a-q-developer-pro-id">Logging in with a Q Developer Pro ID</h2>
<p>Since all Kiro plans include pay-per-use charges, I tried logging in with an IAM Identity Center ID that has Q Developer Pro.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755305047070/8d556aa4-ec73-477e-90f1-1fb147d0c08d.png" alt class="image--center mx-auto" /></p>
<p>When checking the profile in this state, the allowance and usage numbers were gone — likely meaning the account is excluded from Kiro Plan’s limits.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755305069992/c4be606b-ca39-4867-b944-baf9c6baca01.png" alt class="image--center mx-auto" /></p>
<h2 id="heading-session-retention-when-switching-accounts">Session retention when switching accounts</h2>
<p>When switching accounts, IDE-side sessions with Kiro remain intact — no work was lost.  </p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1755305092723/f579ed06-66ce-47ce-8032-e8fd5d3dc79e.png" alt class="image--center mx-auto" /></p>
<h1 id="heading-thoughts-and-whats-next">Thoughts and what’s next</h1>
<p>It seems that the Kiro plan is a bit less favorable compared to Q Developer — perhaps intentionally to promote Amazon Q Developer usage.<br />It’s still unclear whether using Kiro under these conditions will have any restrictions.<br />Personally, I hope that having a subscription to Q Developer would also grant Kiro access (or vice versa). Let’s see how this develops.</p>
]]></content:encoded></item></channel></rss>