LAS VEGAS — After spending nearly two hours trying to impress the crowd with new LLMs, advanced AI chips, and autonomous agents, Amazon Web Services CEO Matt Garman showed that the quickest way to a developer’s heart isn’t a neural network. It’s a discount.

One of the loudest cheers at the AWS re:Invent keynote Tuesday was for Database Savings Plans, a mundane but much-needed update that promises to cut bills by up to 35% across database services like Aurora, RDS, and DynamoDB in exchange for a one-year commitment.

The reaction illustrated a familiar tension for cloud customers: Even as tech giants introduce increasingly sophisticated AI tools, many companies and developers are still wrestling with the basic challenge of managing costs for core services.

The new savings plans address the issue by offering flexibility that didn’t exist before, letting developers switch database engines or move regions without losing their discount. 

“AWS Database Savings Plans: Six Years of Complaining Finally Pays Off,” is the headline from the charmingly sardonic and reliably snarky Corey Quinn of Last Week in AWS, who specializes in reducing AWS bills as the chief cloud economist at Duckbill.

Quinn called the new “better than it has any right to be” because it covers a wider range of services than expected, but he pointed out several key drawbacks: the plans are limited to one-year terms (meaning you can’t lock in bigger savings for three years), they exclude older instance generations, and they do not apply to storage or backup costs.

He also cited the lack of EC2 (Elastic Cloud Compute) coverage, calling the inability to move spending between computing and databases a missed opportunity for flexibility.

But the database pricing wasn’t the only basic upgrade to get a big reaction. For example, the crowd also cheered loudly for Lambda durable functions, a feature that lets serverless code pause and wait for long-running background tasks without failing.

Garman made these announcements as part of a new re:Invent gimmick: a 10-minute sprint through 25 non-AI product launches, complete with an on-stage shot clock. The bit was a nod to the breadth of AWS, and to the fact that not everyone in the audience came for AI news.

He announced the Database Savings Plans in the final seconds, as the clock ticked down to zero. And based on the way he set it up, Garman knew it was going to be a hit — describing it as “one last thing that I think all of you are going to love.”

Judging by the cheers, at least, he was right.

Can the software development hero conquer the “AI Slop Monster” to uncover the gleaming, fully functional robot buried beneath the coding chaos?

That was the storyline unfolding inside a darkened studio at Seattle Center last week, as Amazon’s Kiro software development system was brought to life for a promotional video. 

Instead of product diagrams or keynote slides, a crew from Seattle’s Packrat creative studio used action figures on a miniature set to create a stop-motion sequence. In this tiny dramatic scene, Kiro’s ghost mascot played the role that the product aims to fill in real life — a stabilizing force that brings structure and clarity to AI-assisted software development.

No, this is not your typical Amazon Web Services product launch.

Kiro (pronounced KEE-ro) is Amazon’s effort to rethink how developers use AI. It’s an integrated development environment that attempts to tame the wild world of vibe coding, the increasingly popular technique that creates working apps and websites from natural language prompts.

But rather than simply generating code from prompts, Kiro breaks down requests into formal specifications, design documents, and task lists. This spec-driven development approach aims to solve a fundamental problem with vibe coding: AI can quickly generate prototypes, but without structure or documentation, that code becomes unmaintainable.

It’s part of Amazon’s push into AI-powered software development, expanding beyond its AWS Code Whisperer tool to compete more aggressively against rivals such as Microsoft’s GitHub Copilot, Google Gemini Code Assist, and open-source AI coding assistants.

The market for AI-powered development tools is booming. Gartner expects AI code assistants to become ubiquitous, forecasting that 90% of enterprise software engineers will use them by 2028, up from less than 14% in early 2024. A July 2025 report from Market.us projects the AI code assistant market will grow from $5.5 billion in 2024 to $47.3 billion by 2034.

Amazon launched Kiro in preview in July, to a strong response. Positive early reviews were tempered by frustration from users unable to gain access. Capacity constraints have since been resolved, and Amazon says more than 250,000 developers used Kiro in the first three months.

The internet is “full of prototypes that were built with AI,” said Deepak Singh, Amazon’s vice president of developer agents and experiences, in an interview last week. The problem, he explained, is that if a developer returns to that code two months later, or hands it to a teammate, “they have absolutely no idea what prompts led to that. It’s gone.”

Kiro solves that problem by offering two distinct modes of working. In addition to “vibe mode,” where they can quickly prototype an idea, Kiro has a more structured “spec mode,” with formal specifications, design documents, and task lists that capture what the software is meant to do.

Now, the company is taking Kiro out of preview into general availability, rolling out new features and opening the tool more broadly to development teams and companies.

‘Very different and intentional approach’

As a product of Amazon’s cloud division, Kiro is unusual in that it’s relevant well beyond the world of AWS. It works across languages, frameworks, and deployment environments. Developers can build in JavaScript, Python, Go, or other languages and run applications anywhere — on AWS, other cloud platforms, on-premises, or locally.

That flexibility and broader reach are key reasons Amazon gave Kiro a standalone brand rather than presenting it under the AWS or Amazon umbrella. 

It was a “very different and intentional approach,” said Julia White, AWS chief marketing officer, in an interview at the video shoot. The idea was to defy the assumptions that come with the AWS name, including the idea that Amazon’s tools are built primarily for its own cloud.

White, a former Microsoft and SAP executive who joined AWS as chief marketing officer a year ago, has been working on the division’s fundamental brand strategy and calls Kiro a “wonderful test bed for how far we can push it.” She said those lessons are starting to surface elsewhere across AWS as the organization looks to “get back to that core of our soul.”

With developers, White said, “you have to be incredibly authentic, you need to be interesting. You need to have a point of view, and you can never be boring.” That philosophy led to the fun, quirky, and irreverent approach behind Kiro’s ghost mascot and independent branding. 

The marketing strategy for Kiro caused some internal hesitation, White recalled. People inside the company wondered whether they could really push things that far.

Her answer was emphatic: “Yep, yep, we can. Let’s do it.”

Amazon’s Kiro has caused a minor stir in Seattle media circles, where the KIRO radio and TV stations, pronounced like Cairo, have used the same four letters stretching back into the last century. People at the stations were not exactly thrilled by Amazon’s naming choice. 

Early user adoption

With its core audience of developers, however, the product has struck a nerve in a positive way. During the preview period, Kiro handled more than 300 million requests and processed trillions of tokens as developers explored its capabilities, according to stats provided by the company. 

Rackspace used Kiro to complete what they estimated as 52 weeks of software modernization in three weeks, according to Amazon executives. SmugMug and Flickr are among other companies espousing the virtues of Kiro’s spec-driven development approach. Early users are posting in glowing terms about the efficiencies they’re seeing from adopting the tool. 

Kiro uses a tiered pricing model based on monthly credits: a free plan with 50 credits, a Pro plan at $20 per user per month with 1,000 credits, a Pro+ plan at $40 with 2,000 credits, and a Power tier at $200 with 10,000 credits, each with pay-per-use overages. 

With the move to general availability, Amazon says teams can now manage Kiro centrally through AWS IAM Identity Center, and startups in most countries can apply for up to 100 free Pro+ seats for a year’s worth of Kiro credits.

New features include property-based testing — a way to verify that generated code actually does what developers specified — and a new command-line interface in the terminal, the text-based workspace many programmers use to run and test their code. 

A new checkpointing system lets developers roll back changes or retrace an agent’s steps when an idea goes sideways, serving as a practical safeguard for AI-assisted coding.

Amit Patel, director of software engineering for Kiro, said the team itself is deliberately small — a classic Amazon “two-pizza team.” 

And yes, they’ve been using Kiro to build Kiro, which has allowed them to move much faster. Patel pointed to a complex cross-platform notification feature that had been estimated to take four weeks of research and development. Using Kiro, one engineer prototyped it the next day and shipped the production-ready version in a day and a half.

Patel said this reflects the larger acceleration of software development in recent years. “The amount of change,” he said, “has been more than I’ve experienced in the last three decades.”