Kiro lets teams share a single credit pool to control AI spend
Kiro introduced credit pooling for Enterprise customers: per-seat credits land in one shared pool that the whole team draws from, so capacity left by light users covers heavy users. Admins keep per-user limits and can cap usage at group and profile level, while billing runs through the AWS account.
Key points
- $20 per seat per month with 500 credits contributed to the shared pool each cycle, two-seat minimum.
- Add-on credits cost $0.04 each and roll over up to 12 months; consumption uses included credits first, then the soonest-expiring purchases.
- Limits can be set at profile, group and individual level, with the highest group limit winning for multi-group users.
- Default alerts trigger at 80% and 100%; once a limit is hit, usage blocks until an admin adds credits.
- Groups can be populated from AWS IAM Identity Center, and charges land on the existing AWS bill.
- Third-party identity providers and API access to the governance controls are not available yet.
Credit pooling is Kiro's enterprise pricing model: $20 per seat per month buys 500 credits per billing cycle into one shared pool, with a two-seat minimum. Included credits reset monthly, while add-on credits at $0.04 each last up to 12 months and are spent after the included ones, soonest expiration first.
Governance is layered: limits apply at profile, group and individual level with increasing precedence, and a multi-group user gets the most generous group limit. Hitting a limit blocks usage until an admin buys more, and alerts fire at 80% and 100% by default. Groups can be filled from AWS IAM Identity Center; third-party identity providers and API access are still to come.
Real-world use
- A few developers doing heavy refactoring during a sprint draw on credits that design and data team members never use.
- A platform team caps overnight agent runs with per-user and per-group limits so they cannot produce surprise charges.
- An organization buys add-on credits once in a procurement cycle and plans consumption against the 12-month roll-over.
- An admin automates seat assignment from AWS IAM Identity Center groups and watches assigned versus purchased seats.
Why it matters
It removes the wasted capacity of fixed per-seat allowances and moves cost control from month-end invoice reviews to limits and alerts that act in real time.