Enterprise identity and usage metrics

Since Kiro became generally available on November 17th, we have seen many enterprises like Rackspace, Smugmug and Netsmart adopt the spec-driven development approach across engineering teams to bring more structure in how they develop with AI, seeing increases in efficiency of up to 90% in some cases.

Today, we are making it even easier for organizations to use Kiro with external identity provider support and user-level activity metrics. Enterprises have identity systems, compliance requirements, and teams that need visibility into what's being used and how. The space is changing so quickly that enterprises want to be able to quickly onboard new users and get insights into how and where AI is helping their engineers. With this data, they can quickly scale their tooling and process investments and ship much faster with a consistently high quality bar.

External identity providers: Okta and Microsoft Entra ID

If your organization manages identity through Okta or Microsoft Entra ID, Kiro now plugs directly into that infrastructure. This works across the entire Kiro portfolio — the IDE, CLI, and web app. Your developers authenticate with the credentials they already have, so you don't have to set up new logins.

Once admins onboard your existing identity provider, SSO policies, conditional access rules, and MFA enforcement will be used by Kiro as configured. We started with Okta and Microsoft Entra because that’s what most of you asked for. We are working to support additional OIDC providers. If you’re using a provider not yet supported, let us know because it helps us prioritize.

This is the first step in connecting Kiro to popular enterprise tools and systems, be it identity providers, ticketing and version control systems, deployment tools and more.

User-level activity metrics

Organization admins can now enable user activity reports that provide daily aggregated usage data across your team. The reports break down activity by client type (IDE, CLI, and IDE plugins) so you can see which tools your developers are actually using. These foundational metrics are just the start.

Measuring productivity and establishing usage patterns is something that repeatedly comes up and today we’re building towards not just richer analytics — trend views, team-level aggregations, and exportable dashboards — but insight into how effective use of agentic development drives productivity. Which teams are seeing the best increases in software delivery metrics enterprises care about, and what are the patterns of usage driving those gains? Watch this space in 2026.

What’s next for enterprises

These two features are part of a broader push to make Kiro work within the systems enterprises already rely on. We’re actively working on more integrations with existing tools and services, along with additional governance controls and capabilities that give you the guardrails you need to increase development velocity safely.

If you’re evaluating Kiro for your organization, or already using it and want to see specific enterprise features prioritized, let us know or open an issue on GitHub.