Kiro pricing: Free, Pro, consumption and cancellation

Check Free entitlement

Ongoing Free access has model and capacity conditions different from paid tiers. Try repeated representative tasks rather than only the first request, and inspect what happens at a limit. Distinguish missing model entitlement from insufficient volume before deciding which paid capacity would solve the problem.

Separate monthly and additional spending

The Pro offer is USD20 per user monthly with 1,000 credits. Check additional-usage and account conditions at purchase, including tax treatment. Separate any introductory benefit from the recurring price so a temporary credit is not counted as a permanent reduction in the operating budget.

Do not equate prompts and credits

Specification work, implementation, retries and hooks can consume resources. Prompt count alone is not a reliable unit of cost. Record usage against accepted changes, including rejected attempts, so the budget explains what work consumed capacity instead of assuming every request is interchangeable.

Example: model two workload classes

Suppose your own plan contains twelve small fixes and three investigations. Using measured average consumption Cfix and Cinvestigation, estimate 12Cfix + 3Cinvestigation. This is a hypothetical planning formula, not a guaranteed product allowance. Inspect outliers and retries and decide whether exceeding capacity should pause work or permit extra spending.

Include automatic work

Inspect triggers and actions when enabling hooks. Automatic work can create consumption outside the tasks an operator remembers requesting directly. Pilot only the necessary automation and look for repeated work before buying more allowance. A capacity problem may partly be an inefficient workflow rather than a missing subscription tier.

Check renewal and cancellation

Use the documented account process to move to Free and inspect the current renewal and remaining-credit conditions. Preserve code, specifications and shared guidance. Separately review integrations and billing state, since removing local software or external access is not automatically the same as ending a recurring subscription.

• Choosing Kiro: moving from specifications to implementation
• GitHub Copilot vs Kiro: specification workflow and existing development