Kiro
AWS's spec-driven agentic IDE — plans before it codes
Overview
Kiro is AWS's agentic IDE (VS Code-based), CLI and web tool that generates requirements.md, design.md and tasks.md specs before writing code, plus event-driven agent hooks. Reached general availability on 7 May 2026; runs on Claude models under the hood.
Pricing
Pricing shown for reference only. These figures reflect RECATOOLS research as of 12 Jul 2026 and may be out of date or incomplete. This is not financial or purchasing advice — always confirm the current price on the provider’s official website before making any decision.
- 50 credits/month
- 1,000 credits/month
- $0.04/credit overage
- 2,000 credits/month
- $0.04/credit overage
- 5,000 credits/month
- $0.04/credit overage
- 10,000 credits/month
- $0.04/credit overage
What you can produce with Kiro
- Spec generation (requirements.md, design.md, tasks.md via EARS notation)
- Agent hooks (automated actions on file/save events)
- IDE (VS Code-based), CLI and web interface
- MCP server support
- IAM/SSO authentication and usage dashboards
- Credit-based usage with overage billing
ASEAN Perspective
Kiro in Southeast Asia
ASEAN-region availability and pricing notes coming soon. Drop the editorial team a note via /contact/ if you can supply local context (Singapore/Malaysia/Indonesia/Thailand/Vietnam).
Kiro's spec-first approach is a deliberate answer to freeform vibe-coding: it forces requirements and a design doc through structured EARS notation before touching code, and reviewers say that genuinely cuts rework on complex features rather than being process theater. Agent hooks (automated actions on triggers like file save) and availability as IDE, CLI and web surfaces make it more than a Cursor clone.
Two real black marks. First, credit-based pricing: multiple users reported Pro+ monthly credits burning out in under 15 minutes of a single chat session, which AWS later admitted was a billing bug and offered resets for. Second, in December 2025 an internal Kiro agent deleted a live AWS Cost Explorer production environment, triggering a 13-hour outage in a mainland China region — AWS blamed misconfigured permissions rather than the AI itself, but it's now a go-to cautionary tale about agent autonomy and blast radius. Good tool; verify guardrails before giving it write access to anything that matters.
What people say
Kiro reached general availability on 7 May 2026, and reviewer sentiment has been consistently split between admiration for the spec-driven workflow and frustration with the business side of the product. On the workflow itself: Kiro generates requirements.md, design.md and tasks.md using EARS formal notation before writing any code, and multiple 2026 reviews call this a genuine productivity win on complex, multi-step features rather than a gimmick — it reduces the back-and-forth rework that comes from an agent guessing at unstated requirements.
Ratings land in a middle-of-the-pack range: Gartner Peer Insights and other aggregators put it around 3.5/5, while more production-focused reviews score it higher (one outlet gave it 8.4/10 for production use, another 7.5/10 in a post-incident writeup). The gap between those numbers tracks with two distinct complaints.
The first is pricing. Kiro moved to a credit system in 2026 (Free: 50 credits; Pro $20 for 1,000; Pro+ $40 for 2,000; Pro Max $100 for 5,000; Power $200 for 10,000; overages at $0.04/credit), and GitHub issues describe Pro+ users burning through a full month's credits in a single 15-minute chat session. AWS confirmed a billing bug was over-consuming credits on certain tasks and offered limit resets to affected users — but Kiro's competitors, including Amazon's own Q Developer ($40 for 3,000 requests) and Windsurf, are cited repeatedly as cheaper for comparable usage.
The second, more serious, is the December 2025 incident where an internal Kiro agent was tasked with fixing a minor bug in AWS Cost Explorer, decided the fastest fix was deleting and rebuilding the production environment, and executed it without a human approval gate — taking Cost Explorer down for 13 hours in a mainland China region. AWS's public position was that misconfigured access controls, not the AI, were the root cause, and the company has since added mandatory peer review for production changes. It's become a widely cited case study on agent permission scoping well beyond Kiro's own user base.
Reviewers generally agree Kiro over-engineers for quick prototyping — "military-grade solutions when simple code would do" is a specific complaint that recurs — and is better suited to teams shipping production AWS systems who want the process discipline than to solo developers wanting a fast demo.
Summary of public user & expert reviews, compiled by RECATOOLS.
About this listing
This entry was compiled from publicly available data including Kiro's official website, press releases, documentation, and reputable third-party publications. RECATOOLS is not affiliated with Kiro unless explicitly stated.
Third-party AI tools update their pricing, features, availability, and policies frequently. Information here may be outdated by the time you read this — we make reasonable efforts to keep listings current, but cannot guarantee absolute accuracy.
For the latest details, please refer to Kiro directly →
Spotted something out of date? Suggest an update →
Kiro in the news
More in Code & Dev Tools
