Want to try it?. Join the waitlist at What do you think about usage-based pricing for AI dev tools? Worth the transparency trade-off?

The logic: research shows addressing issues during planning is 5x to 7x more cost-effective than fixing them during implementation. Pricing reflects this reality:.• Planning conversations (vibe) = lower cost .• Execution tasks (spec) = higher cost

Why separate spec vs vibe pricing?. Spec requests = structured task, typically longer execution times and more complex ("execute task 1", running multiple tasks). Vibe requests = chat interactions ("explain this code", creating specs). Different computational costs, different

Instead of forced upgrades, pay per extra request. On the $40 plan but need 10 more spec requests? That's $2 extra, not a jump to the $200 tier. $0.20/spec request, $0.04/vibe request.

The usage dashboard lives right in your IDE. Track spec/vibe requests, see remaining allocation, monitor potential overages in real-time.

Kiro's new usage tracking gives you more control. 🔗 Real-time visibility into what you're actually using, plus flexible overage pricing instead of forced tier jumps. Here's how it works: 🧵

Want to set up an MCP server in Kiro but don't know where to start? We've got you covered! Watch how to do it in 3 simple steps. To learn more checkout the full blog post 🔗 #Kirodotdev #BuildwithKiro #AIcoding

We announced our pricing model last week and you had questions. 🔗 "What's a spec vs vibe request?" ."How do I track usage?" ."What if I go over my plan?". Instead of forcing expensive tier upgrades, we built flexible overages so you pay for what you.

100k+ developers in our first week. We're blown away!. We launched Kiro in preview expecting to hit capacity over a few months. You all embraced it in just days. 👻 🤍 . To everyone on the waitlist: We've started onboarding thousands of developers from the waitlist this week. For

Join us for our first live Q&A session with the Kiro team! Learn about Kiro and spec-driven development from the team building it. Whether you're just starting out or a Kiro pro, drop in and chat with our team! . Starts at 9 AM Pacific on Discord 👉

Kiro Bi-Weekly Show | Spec-driven development - the future of software development

Do you think spec-driven development is the future? Lets chat about this LIVE on Twitch tomorrow at 9 am PST. 🔗 #BuildwithKiro #Kirodotdev

We're evolving Kiro with you. New pricing tiers are coming soon & we’re opening our waitlist starting next week: . • Two-week free trial for new users .• Perpetual free tier .• Paid plans from $20/mo .• Separate Vibe & Spec allocations . Details in our blog 👉

Looking to build apps that can search the web, images, videos and more? @brave just made it incredibly simple to connect your Kiro projects with real-time access to the web using their latest MCP server for Brave Search. Learn more 👉

Introducing Kiro Agent Hooks! Your IDE can now proactively update tests, sync docs, and apply coding standards automatically. Say goodbye to repetitive tasks and hello to intelligent workflows that anticipate your needs. Checkout the full blog 👉

RT @mreferre: Blown away by your response to Kiro. 100k+ joined our preview in week one, more than we expected. We've added a waitlist. To….

AI Coding with Friends | Meet Kiro 👻

We’re going live at 9 AM PST on Twitch! 👻.Join us as we break down how your feedback is shaping Kiro, built for devs, by devs. Got questions? Bring ’em! Let’s geek out over code together. #KiroDotDev #BuildwithKiro #CodingwithAI

Join us live on July 22 at 9 am PST 👻 . Listen in as we chat through our plans on using your direct feedback to keep Kiro a tool for devs, by devs. So, bring your questions and let's geek out over some code together. #KiroDotDev #BuildwithKiro

🚀 Thank you for your amazing response to Kiro! We're seeing unprecedented demand. To ensure we can continue to provide the experience our community loves, we’ve implemented a waitlist as we fine tune Kiro. 👉 Sign up here