Loading image...Kiro

Product

  • About Kiro
  • Agents
  • IDE
  • CLI
  • Web
  • Mobile
  • Crew
  • Pricing
  • Downloads

For

  • Enterprise
  • Startups
  • Students

Community

  • Overview
  • Ambassadors
  • Case studies
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase

Resources

  • Docs
  • Blog
  • Changelog
  • FAQs
  • Videos
  • Report a bug
  • Suggest an idea
  • Billing support

Social

Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
Kiro
  • Agents
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Kiro

Get Started

InstallationAuthenticationYour first project

Models

OverviewAvailable modelsReasoning effortAWS GovCloud (US) models

Features

How Kiro worksLocal command sandboxACP integrations
Specs
Steering
Hooks
MCP
Permissions
Custom agents
Workflows
Agent Skills
Powers
Cloud sessionsMemoryCompactionKiroignoreCheckpoints and rewind
Built-in tools
Configuration scopes

IDE 1.x

What's new in 1.0
Setup & First Run
Editor
Chat
Experimental
Troubleshooting0.x reference

CLI

Setup & First RunChoose an agent harness
Terminal UI
Chat
Fullscreen modeVoice modeHeadless modeACPAuto complete
Experimental
Troubleshooting
Upgrade from CLI 2.x
2.x reference

Crew

Quick startInstallationRunning 24/7
Chat
Agent Capabilities
Features
Interfaces
Apps
System & storageConfigurationSecurityTroubleshooting

Web

Setup & First RunIdentity Center
Connect your repositories
Working with the agent
Autonomous modeScheduleConfiguration Sync
Sandbox

Mobile - Preview

Overview

Commands and Reference

CLI commandsSlash commandsBuilt-in toolsExit codesSettings

Billing

OverviewManaging your subscriptionUpgrading your planDowngrading your planCancelling your planPurchasing add-on creditsManaging your paymentsManaging usage notificationsManaging your taxesContacting billing supportDeleting your accountRelated questions

Enterprise

ConceptsOnboarding quickstart
Connecting your identity provider
Deployment optionsSubscribe your teamManage subscriptions
Credit pooling
Overview
Manage seats
Manage usage limits
Monitor usage
Add credits
Governance
Monitor and track
SettingsManaged updatesTLS inspection compatibilityBillingIAMSupported regions
AWS GovCloud (US)

Privacy and Security

OverviewData protectionCode referencesCompliance validationInfrastructure securityIAM permissionsFirewalls, proxies, and data perimetersVPC endpoints (AWS PrivateLink)

Guides

OverviewRunning Kiro in the cloud
Language support
Learn by playing

Migration

Migrating from Q DeveloperMigrating from VSCodeUpgrading from Q CLI
  1. Docs
  2. Enterprise
  3. Credit pooling
View as Markdown

Credit pooling

View as Markdown

Credit pooling gives your organization one shared pool of Kiro credits instead of a separate credit allowance for each subscriber. You add users and groups, and every seated member draws from the same pool while you decide how many credits each user can use, directly or through group and profile limits. In the Kiro console, this feature is labeled Credit sharing.

IAM Identity Center required

Credit pooling currently supports only Kiro profiles using AWS IAM Identity Center. Profiles connected directly to an external identity provider cannot use credit pooling.

Before using credit pooling, update your administrator policy with the credit-pooling actions in the full Kiro administrator policy. The full example also grants permissions outside credit pooling.

Benefits

  • One shared pool. Credits no longer sit unused with individual users; what one person does not use stays available to everyone else in the pool.
  • No overages or unexpected spikes. The pool is the spending boundary for the users in it.
  • Less administration. You manage seats, credits, and limits for the pool instead of managing each individual subscription.
  • No additional cost to enable. Enabling credit pooling is free. You pay $20 per seat per month, and each seat contributes 500 shared credits per month.

How credit pooling works

  • Seats. Each seat costs $20 per month and contributes 500 monthly credits to the pool. Buying seats adds those credits to the pool right away; you do not need to assign a user to a seat for its credits to count. Seat price and credits are prorated for the first month, and the full seat price is due at the next billing cycle. Seats you add later are prorated the same way.
  • Monthly credits. The console calls the credits that seats contribute monthly credits (also known as included credits). Kiro uses monthly credits first, and unused monthly credits expire at the end of the billing cycle.
  • Additional credits. When the pool needs more, you buy additional credits as a one-time purchase. They are added to the shared pool and are good for one year from the purchase date. After monthly credits run out, Kiro uses the additional credits with the earliest expiration date first.
  • Usage limits. You can cap how many credits each user can use. A user-level limit takes priority over group limits, the highest matching group limit comes next, and the profile limit is the fallback for users without either limit.

Understand your billing model

Pools are billed either prepaid or postpaid. The billing model is set for your AWS account and is shown in the purchase summary and on the Credits tab. Prepaid pools show the Add seat purchase action and assign seats as described in Manage seats. Postpaid pools seat members automatically.

Choose a setup path

Your situationPath
New Kiro customer with a fresh Kiro profileCredit pooling is the only option offered. Follow Set up a fresh profile.
Existing customer with users on individual subscriptionsMove them with the Switch to credit sharing wizard. Follow Switch existing subscribers.
Credit pooling is already enabledAdd people with Manage seats.

Set up a fresh profile

  1. Set up seats. For a prepaid pool, open Access management > Credit sharing and choose Add seat. Enter the number of seats in How many seats do you want?, review the Buy seats purchase summary, and choose Confirm Purchase. Each seat adds 500 monthly credits to the pool. A postpaid pool does not show Add seat; skip to adding users and groups. See Understand your billing model.
  2. Add users and groups. Choose Add user or Add group and search IAM Identity Center or your synced identity provider. Every user in a prepaid pool needs a seat. If you add more users than you have free seats, the console adds the extra users with Awaiting seat status and opens the Add seat checkout for the shortfall. After the purchase completes, those users remain in Awaiting seat status until they activate their Kiro account from any Kiro client.
  3. Check your credits. Each seat contributes 500 shared credits per month. If your teams need more, choose Buy more credits to add additional credits. See Add credits.
  4. Set usage limits. Cap the credits each user can use, directly or through group and profile limits. See Manage usage limits.

For seat assignment, shortfalls, and removing users, see Manage seats.

Switch existing subscribers

Switching is irreversible

After you switch users to credit sharing, you cannot switch them back to individual subscriptions.

  1. In the Kiro console, open Access management > Subscriptions and choose Switch to credit sharing. The Switch to Kiro Credit Sharing wizard opens.
  2. In Step 1, How it works, review the seat price and credits, then choose Select users and groups.
  3. In Step 2, Select users & groups, select the users and groups to move to the pool. For external identity providers, group sizes are not available, so members of the selected groups are not included in the totals shown; your actual credits and cost will be higher than the wizard total.
  4. In Step 3, Review & enable, compare Current cost with Cost with credit sharing. Your bill is prorated for the remaining days in the current billing cycle. Users who appear in more than one group are counted once and are not charged twice.
  5. Choose Enable credit sharing.

You can also move people from the Subscriptions tab with Add user to Credit Sharing or Add group to Credit Sharing in the Add user and Add group menus.

What happens to individual subscriptions

  • The switch cancels each user's individual subscription. If you switch a user mid-month, your account is charged a prorated amount for the days the individual subscription was used, and the user's seat contributes a prorated share of its 500 monthly credits for the remaining days of the month.
  • If the cancellation fails, the console warns that the subscription is still active and still billed. Deactivate it from Access management > Subscriptions > Users.

Related resources

  • Manage seats: Buy seats, add users and groups, assign seats, and remove them
  • Manage usage limits: Control each user's usage with user, group, and profile limits
  • Monitor usage: Track pool balance and projected consumption
  • Add credits: Buy additional credits to top up the shared pool
  • Enterprise billing: Understand subscription tiers and included credit allowances
  • Managing Kiro subscriptions: Change plans, unsubscribe users, and manage overages for individual subscriptions

Next step

Go to Manage seats to buy seats and add your first users and groups.

Page updated: November 4, 2026
Manage subscriptions
Manage seats