Kiro Pricing (September 2026): Plans, Credits, Overage, and What the Meter Actually Means

Summary

If you searched for kiro price or kiro pricing, here is the plan card as verified on September 14, 2026. Kiro sells five self-serve tiers: Free at $0 with 50 credits, Pro at $20 per user per month with 1,000 credits, Pro+ at $40 with 2,000 credits, Pro Max at $100 with 5,000 credits, and Power at $200 with 10,000 credits. Enterprise is custom pricing billed through AWS. Every paid tier bills extra usage at $0.04 per credit.

Tier prices and credit counts are unchanged since July 2026, re-checked September 14, 2026. The trial is what changed. The old 500 bonus credits usable within 14 days ended on May 8, 2026. First-time upgraders now get $20 credited toward the first paid subscription, which Kiro states is worth 1,000 credits, using social login or an AWS Builder ID. Monthly credits do not roll over. Purchased add-on credits last 12 months.

Kiro Plan Breakdown (September 2026)

Here is the public price card without padding or speculation, read from kiro.dev/pricing on September 14, 2026.

Kiro Pro Vs Pro+ Vs Pro Max Vs Power: Which Tier To Buy

All four paid tiers are the same product. The only variable is how many credits land in your account on the first of the month. Every tier buys credits at $0.02 each, so the tier question reduces to one number: your steady-state monthly credit burn.

The break-even rule is mechanical. Buying more than 500 add-on credits in a month costs more than the $20 step to the next tier, so a Pro user who routinely buys two $10 packs should be on Pro+. Because monthly credits expire and add-on credits last 12 months, the opposite is also true: if your usage is spiky rather than steady, sizing down a tier and topping up with packs keeps the unused balance alive instead of burning it at each reset.

How Kiro Credits And Overage Work

Paid plans include a monthly block of credits. Usage beyond that block is sold as add-on credits at $0.04 per credit, charged immediately at purchase rather than billed at month end.

The add-on credit docs set hard limits on that purchase, checked September 14, 2026:

• Minimum purchase is $5 for 125 credits.
• Maximum is $100 per pack, with up to five packs held at once.
• Plan credits are always consumed first, then add-on credits.
• Add-on credits expire 12 months after purchase, soonest-expiring pack first.
• Monthly plan credits do not roll over.
• Free tier accounts cannot buy add-on credits at all.
• Subscriptions are individual, not shared.

Kiro sends a low-resource notification at 80% of monthly credit usage. When both plan credits and add-on credits are exhausted, the account pauses until you buy more or the billing cycle resets.

Monthly cost = plan price + add-on credits purchased

Add-on cost = credits bought * $0.04   (min $5 / 125 credits per pack)

Plan rate  = $0.02 per credit   ($20 / 1,000 on every paid tier)
Add-on rate = $0.04 per credit  (exactly 2x the plan rate)

What N credits cost:
- 1,000 credits = $20 as the Pro plan allotment, $40 as add-on credits
- 2,000 credits = $40 as the Pro+ plan allotment, $80 as add-on credits
- 5,000 credits = $100 as the Pro Max allotment, $200 as add-on credits

Examples:
- Pro user at 1,000 credits used = $20
- Pro user at 1,250 credits used = $20 + (250 * $0.04) = $30
- Pro+ user at 2,300 credits used = $40 + (300 * $0.04) = $52

Break-even: buying more than 500 add-on credits in a month
costs more than the $20 step up to the next tier.

How Many Tokens Is a Kiro Credit? Credit Cost per Model and Request

This is the question the pricing page does not answer, and it is the one that determines your bill. Kiro publishes no token-per-credit conversion rate. There is no figure in the pricing page, the billing docs, the models docs, or the FAQ that converts a credit into a token count. A credit is not a repackaged token bundle.

What a credit is actually metered on, quoted from Kiro's FAQ as of September 14, 2026: "a unit of work in response to user prompts. Simple prompts can consume less than 1 credit. More complex prompts, such as executing a spec task, typically cost more than 1 credit." Credits are metered to the second decimal place, with 0.01 as the minimum charge. The available-models docs tie consumption to the output tokens a model generates, which is why the same prompt costs different amounts on different models.

On top of that, every model carries a published credit multiplier. These are the multipliers explicitly listed on the available-models page, checked September 14, 2026:

Two consequences follow. First, a Pro plan is not "1,000 requests": at 2.4x on Sol, 1,000 credits buys one forty-eighth of the work the same 1,000 credits buy at 0.05x on Qwen3 Coder Next. Second, the Auto router is the 1.0x baseline, and Kiro's FAQ states that running the same task on Sonnet 4.6 costs about 1.3x what Auto costs. Leaving Auto selected is the default cost control.

What Changed In Kiro Pricing Since July 2026

The plan card did not move. The tiers, credit counts, and the $0.04 add-on rate are identical to July 2026, re-checked September 14, 2026. What moved is around the edges, and it is visible in the public issue tracker rather than on the pricing page.

• Credit burn per task is contested. An issue filed in the Kiro repository on July 16, 2026 and still open reports that before late June 2026 an ordinary one-file change or a single focused test file consumed no more than roughly 10 credits, and runs above roughly 20 credits were uncommon. After late June, the same reporter measured simple one-file changes at roughly 20 to 30 credits, with several runs at 30 to 35. At those numbers a Pro plan's 1,000 credits covers roughly 30 to 50 such runs. Kiro has not published a response confirming a change to credit accounting.
• A second report landed in September. A separate issue filed September 11, 2026 against Kiro 1.0.437 reports credits being consumed significantly faster after the last two updates with an unchanged usage pattern, and asks Kiro for a per-action breakdown of how credits are consumed. No such breakdown is published today.
• Overage enforcement is not uniform across platforms. An issue filed September 12, 2026 and labelled by the maintainers under pricing reports that with overages enabled the agent refuses to continue past the limit on Linux while the same flow works on the macOS client. Budget for this if your team is not on macOS.
• Students get 1,000 credits per month. The Kiro for students terms, last updated September 8, 2026, grant eligible students 1,000 credits per month for 12 months, equivalent to the Pro allotment. Eligibility requires being 18 or older, enrolled at a participating university, and using a valid university email. Unused credits do not roll over, students cannot buy add-on credits during the benefit period, and accounts drop to the Free tier when the 12 months end.

Kiro Enterprise Pricing And Pooled Credits

Enterprise is custom pricing and is not listed on the public plan card. What the docs do specify, checked September 14, 2026: it adds centralized billing, SSO, usage analytics, and enterprise security. Users are added and subscribed through the AWS console, with access via IAM Identity Center, Okta, or Microsoft Entra ID. Overages are disabled by default and bill at $0.04 per credit at month end when an administrator turns them on. The Free tier is not available inside an Enterprise account, and it is also unavailable in AWS GovCloud regions.

On the question people actually search for: Kiro credits are not pooled. The enterprise concepts documentation states that when you subscribe a group to Kiro, the users within it are subscribed individually. Credits land per user. A feature request opened in the Kiro repository on March 12, 2026, labelled by the maintainers under pricing and still open, asks for exactly this: credits defined at a group level so they can be pooled and shared on a first-in-first-out basis, because under-using developers waste credits in the same month that over-using developers run out. A related request filed August 31, 2026 and closed as a duplicate notes the same gap for overage caps, which are enforced per user rather than as one shared ceiling for a profile.

The practical effect: an enterprise with uneven usage pays for the peak of every individual rather than the average of the team. There is no committed-spend pool to draw down and no way to let a heavy user borrow an idle teammate's credits.

How To Evaluate Whether Kiro Pricing Is Actually Good For You

Kiro is reasonably priced if you want its IDE workflow and you stay inside the included credit range. It gets expensive when your usage is bursty, when you need pooled team billing, or when your actual problem is narrower than "I need another AI IDE."

The pricing page itself is not the hard part. The hard part is being honest about the job you need done. If your team wants planning, interactive IDE assistance, and per-user subscriptions, Kiro is easy to understand. If you want a backend primitive for applying model output into real files, the fit changes.

Kiro Pricing Vs Morph For Code-Apply Workflows

These are different products, so compare the unit of value rather than the sticker price. Kiro is an AI IDE sold as a per-user subscription metered in credits. Morph Fast Apply is an API: send an instruction, the original code, and the update, get the merged file back. It is billed per token with no seat and no credit meter.

Morph Fast Apply rates, from the pricing configuration in this repository: morph-v3-fast is $0.80 per million input tokens and $1.20 per million output tokens. morph-v3-large is $0.90 per million input tokens and $1.90 per million output tokens. Both carry a 262,144-token context window. A single apply call sending 2,000 tokens of input and returning 1,000 tokens on morph-v3-fast costs $0.0028.

If you are evaluating kiro pricing because you want a stronger planning-oriented IDE, that is a legitimate reason to choose it, and nothing here argues otherwise. If you are evaluating it because you need edits merged into files with less friction, Kiro is solving a broader problem than the one you have, and you are paying a seat price for it.

FAQ

Kiro plan, credit, trial, and enterprise facts on this page were read from kiro.dev/pricing, kiro.dev/faq, and the Kiro billing and models documentation on September 14, 2026. Practitioner reports are cited to dated issues in the public kirodotdev/Kiro repository.