TL;DR:

  • Amazon Q Developer is AWS’s inline coding assistant — autocomplete, chat, and code review integrated into VS Code, JetBrains, and the AWS Console
  • Kiro is a new spec-driven coding IDE that turns a written requirement into tasks, then implements them autonomously across multiple files
  • They solve different problems: Q Developer augments your current workflow; Kiro is a separate environment for building features from scratch

Amazon now ships two distinct AI coding products with different philosophies and use cases. If you’re trying to decide which to adopt, you need to understand that they’re not competing for the same job.

Amazon Q Developer: The Inline Assistant

Amazon Q Developer is the evolution of CodeWhisperer, Amazon’s original code completion product. It sits inside your existing IDE as a plugin and works similarly to GitHub Copilot:

  • Inline autocomplete — suggests the next line or block as you type, trained on AWS-heavy code including CloudFormation, CDK, and Terraform
  • Chat interface — ask questions, explain code, generate functions, refactor existing code
  • Code review — scan for security vulnerabilities, AWS-specific misconfigurations, and code quality issues
  • CLI integration — q chat in your terminal gives you an AI assistant that understands your shell context
  • AWS Console integration — Q Developer appears inside the AWS Console, letting you ask questions about your resources or generate IAM policies

The primary audience for Q Developer is developers who are already deep in the AWS ecosystem. Its training data skews heavily toward AWS services, and it’s noticeably better than general-purpose coding assistants at IAM policy generation, CDK construct syntax, and CloudFormation template structure.

Q Developer has a free tier (50 chat interactions and limited code completions per month) and a Pro tier at $19/user/month that removes limits and adds organizational controls.

Kiro: Spec-Driven Agentic Development

Kiro is a standalone IDE built on VS Code’s editor foundation but designed around a different workflow: you write a specification, and Kiro converts it into a set of tasks, then implements those tasks across your codebase autonomously.

The workflow looks like this:

  1. Write a spec in natural language — describe a feature, a new module, or a set of requirements
  2. Kiro generates a task list — it breaks the spec into concrete implementation steps and shows you the plan before touching any code
  3. Review and approve the plan (you can edit tasks before execution)
  4. Kiro implements — it writes code across multiple files, creates tests, updates configuration, and produces a diff for your review
  5. You review and approve the diff before it’s committed

This is meaningfully different from the “generate one function at a time” model of Q Developer or Copilot. Kiro is doing multi-file, multi-step agentic work from a starting requirement rather than completing what you’re already typing.

Kiro has built-in support for hooks — you can define what should happen before a spec is executed (run existing tests, validate the plan against your architecture docs) and after (run tests again, check for linting errors). This makes it possible to build CI-like gates into the agentic workflow rather than treating Kiro’s output as automatically trustworthy.

The Core Difference: Completion vs. Construction

The most useful way to think about the difference is the starting point of the work:

Q Developer starts from your cursor. You’re writing code and Q Developer helps you write it faster. The intelligence is assistive — you’re directing the work and the AI accelerates execution.

Kiro starts from a requirement. You write what you want built, and Kiro plans and executes the construction. The intelligence is directive — Kiro is doing the work and you’re reviewing and approving.

These are genuinely different modes of working with AI, and they suit different situations.

When to Use Amazon Q Developer

Q Developer fits naturally into your current development workflow without requiring a context switch. Use it when:

  • You’re writing code in an existing codebase and want autocomplete and inline suggestions
  • You need to quickly understand unfamiliar code (/explain command works well)
  • You’re working heavily with AWS services and want assistance that understands CloudFormation, CDK, and IAM syntax specifically
  • You want code security scanning without a separate tool
  • Your team uses AWS Identity Center or IAM Identity Center and wants centralized SSO for the AI assistant

For AWS-specific work — writing CDK stacks, debugging Lambda functions, generating correct IAM policies — Q Developer is better than Copilot or Claude Code because of its AWS-specific training data.

When to Use Kiro

Kiro makes more sense when:

  • You’re starting a new feature or module from a clear requirement rather than filling in existing code
  • The work involves multiple files that need to be created or modified consistently
  • You want the AI to plan before executing, with the ability to review and modify the plan
  • You’re comfortable with an agentic workflow where the AI makes decisions autonomously between your approval checkpoints

Kiro is better suited to greenfield feature development than to incremental changes in existing complex codebases. If you’re adding a completely new API endpoint with associated data models, validation, tests, and documentation, Kiro’s spec-driven approach handles that coherently. If you’re fixing a subtle bug in existing code, Q Developer’s inline assistance is faster and less disruptive.

Pricing and Access

Amazon Q Developer Free:

  • 50 chat messages per month
  • 1,000 inline code completions per month
  • Security scanning included
  • No cost, no credit card

Amazon Q Developer Pro:

  • $19/user/month (billed through AWS)
  • Unlimited chat and completions
  • Organization-level management
  • AWS IAM Identity Center integration

Kiro:

  • Free preview access during the launch period (as of mid-2026)
  • Pricing post-preview not yet announced; expect it to be positioned above Q Developer Pro

Can You Use Both?

Yes, and many developers on AWS-heavy teams will end up using both. Q Developer is a lightweight plugin you keep active in VS Code or IntelliJ all the time. Kiro is a separate application you open when starting a new feature from spec.

The workflows don’t conflict — Q Developer helps you while you’re in Kiro reviewing and editing Kiro’s output, if you have both open. They share AWS credentials if you’re signed into AWS Builder ID.

The Bottom Line

If you’re primarily asking “should I switch from GitHub Copilot to an Amazon product” — Q Developer is the direct comparison, and it wins specifically for AWS workloads due to better AWS-specific training.

If you’re asking “what’s the most autonomous AI coding workflow for building new features” — Kiro is the more interesting product, and it’s worth evaluating if your team is comfortable with the spec-driven, agentic approach.

Neither replaces the other. They address different phases of the development process, and Amazon’s strategy of shipping both rather than forcing one tool to do everything is reflected in how different they feel to use.