fshy

fshy / Coding subscriptions

Kiro

kiro.dev · Coding subscriptions · 1 record · JSON

Kiro Coding subscriptions

caveatemailno cardDrequest-rate

kiro.dev/pricing/ · coding subscription · coding-subs/kiro · JSON · compare

Free tierKIRO FREE: USD 0 per month, 50 credits, access to open weight models and Claude Sonnet 4.5
unit requests; metered on request-count; a credit is the metering unit; the page does not state what one credit buys
Pricenone stated
Per-object capnot applicable: a subscription meters usage, not objects
Retentionnot applicable
Egressnot applicable: the vendor serves the inference
Identityemail social login or an AWS Builder ID. The free-model note names social logins and Builder ID specifically, so the gate is not identical across sign-in routes
Limits
  • request-rate 50 credits a month on Free; 1,000 on Pro at USD 20; 2,000 on Pro+ at USD 40; 5,000 on Pro Max at USD 100; 10,000 on Power at USD 200 source
Bindingrequest-rate
Interfacecli the Kiro IDE; sign-in is by social login or an AWS Builder ID
ToolingKiro desktop IDE
Composes withthe Free tier is the same account and the same model set as Pro, so a measurement taken today stays valid if the account is later upgraded
Reliabilityno reliability event recorded
Notes50 credits a month against 1,000 on a USD 20 plan is 5 per cent of the paid allowance, which is the smallest free-to-paid ratio in the class.
Evidence rungdocumented the ladder is quoted from the vendor page read today. The credit-to-token conversion is unpublished, so capacity in tokens is unverified. verified_at is the instant its evidence URLs were fetched on 2026-10-22, read from the fetch log, not typed.
Checked2026-10-23 (live); stale on 2026-11-22
Parsed numbers
  • $.limits[0].value limit:request-rate 50.0 credits / month
Evidence (1)
datesourcewhat it proved
2026-10-22kiro.dev/pricing/Free USD 0 with 50 credits; Pro USD 20 with 1,000; Pro+ USD 40 with 2,000; Pro Max USD 100 with 5,000; Power USD 200 with 10,000; add-on credits USD 0.04 each
Unknown or withheld values (2)
  • $.reliability_note none-observed
  • $.retention.stated not-applicable