One year of Kiro: a look back, and a look ahead - Kiro<br>Back to all posts<br>A year ago today, we introduced Kiro to the world with a simple belief: developers deserve better than vibe coding. They deserve tools that help them think clearly, build confidently, and ship production-ready software without trading speed for quality.<br>What happened next humbled us, occasionally set us (metaphorically) on fire, and made Kiro what it is today. None of it would have happened without you.<br>From preview to production

When we launched Kiro IDE in preview last July, we knew spec-driven development resonated with how experienced engineers actually work. But we didn't know to what extent the broader developer community would embrace it, and we underestimated you all. More than 100,000 developers tried Kiro IDE within the first 5 days, and demand kept climbing from there. By October, that number had more than doubled. The response was incredible and taught us that you would tell us exactly what you thought, loudly and quickly.<br>In November, we took Kiro to general availability with a set of capabilities we were proud of. We were the first to bring spec-driven development to AI coding tools, and we doubled down on features that brought even more reliability and rigor. Property-based testing that measures whether your code matches your spec. Checkpointing to rewind agent-made changes. We launched Kiro CLI that bringing agentic development to your terminal. And enterprise features for organizations ready to adopt Kiro at scale.<br>Since then, the pace has only picked up: remote MCP, global steering files, our Auto agent. Parallel agents that learn across sessions. Multi-root workspace support. GovCloud availability. Powers for extending what Kiro can do, Agent Focus to enable agent-centric building, and new plans with Kiro Pro Max. And a growing roster of models from Anthropic, OpenAI, and open weight models, so you can choose the right model for the job.<br>We’ve also launched Web and Mobile experiences so you can work with Kiro wherever you are. Every Kiro surface is optimized for a different style of development work: the IDE for hands-on, code-heavy building; the CLI for terminal-native workflows, CI/CD, and DevOps-aligned automation; Web where autonomy and collaborative building is the core experience; and Mobile as a control hub across your cloud sessions, so your phone keeps work moving without locking you to a laptop. With Kiro working from your preferences, rules, and repos across each, you can flex into whichever surface fits how you’re working on any given day.<br>And among growing roster of models from Anthropic and open weight models, I am excited to share we’ve added OpenAI’s GPT-5.6 Sol, Terra, and Luna models live across the IDE, CLI and Web. These models are tuned for different performance-cost optimizations so you can get the most from your credits: Sol for complex multi-step work, Terra for the standard fare, and Luna for fast and low-cost throughput. With these added to the arsenal we continue to prioritize providing more models to you for more choice as you build.<br>Our builders inspire us

As we’ve been building Kiro, our community has continued to be our guiding hand, and as a result Kiro developers have been doubling over quarters. The stories we’ve heard from builders this year remind us why we do this work.<br>Rob Larmon and his two-person cloud team at Loyola Marymount University used Kiro to update 500 Lambda functions across dozens of AWS accounts. A task that previously took two months now takes half a day. Rob told us Kiro feels like having "a three-to-ten-person development team at my fingertips." He’s now running Kiro workshops across campus, training the next generation of builders.<br>Students have been just as inspiring. Since launching Kiro for students, thousands of students have joined the Kiro community and are receiving 1,000 credits per month free for a year. The next generation of developers is learning to build with intention from day one. Olivia Herneddo, Lead Experience Designer at Arizona State University, worked with our team to bring Kiro into an ASU hackathon, and shared with us the feedback from one hacker that captured the whole thesis of Kiro:<br>“Kiro made the spec-first approach feel natural rather than bureaucratic. Writing requirements and correctness properties before code meant we always knew what we were building toward, and when we hit an inevitable mid-build pivot, the specs absorbed the change cleanly instead of breaking everything.”<br>Startups have been equally enthusiastic. When we launched Kiro for startups, thousands of founders applied and demand was so high we had to close applications early. We brought the program back a few months later, so that qualifying early-stage teams can now get a full year’s worth of Kiro Pro+. It’s clear that small teams building fast need structure just as much as large enterprises do.<br>For lean startup Analytics Fox Softwares, Kiro's spec-driven workflow...