KirovsKun
Generated from the two spec rows. Green marks the better value where a spec has a clear direction. Everything else is just different.
Kiro
Amazon Web Services · AI-native IDE
#57MCP
Panel
6.53 spec wins
- Reliability
- 6.3
- Usefulness
- 6.7
- Cost
- 5.7
- Longevity
- 7.3
“Makes you write requirements, design and tasks before any code, so the credit meter starts running before the first line does.”
Kun
KunAgent · AI-native IDE
#84MCP
Panel
5.84 spec wins
- Reliability
- 5.7
- Usefulness
- 6.2
- Cost
- 6.5
- Longevity
- 4.8
“It writes your code and also your slide deck, which is the most accurate description of an engineering week ever shipped as a feature list.”
Spec by spec
| Spec | Kiro | Kun |
|---|---|---|
| Architecture | ||
| Category | AI-native IDE | AI-native IDE |
| Runs | local, cloud, sandbox | local |
| Platforms | macos, linux, windows, web | macos, linux, windows |
| Context window | not documented | not documented |
| Protocols | ||
| MCP client | Yes | Yes |
| MCP server | No | No |
| Capabilities | ||
| Runs terminal commands | Yes | Yes |
| Multi-file edits | Yes | Yes |
| Git operations | Yes | Yes |
| Browser control | YesEvery Kiro Web sandbox ships a headless Chrome with Playwright MCP, the agent-browser CLI and the Chrome DevTools MCP server preinstalled; the local IDE and CLI have no built-in browser tool. | YesBrowser output is attached to tasks and screenshots are captured through browser automation. |
| Sandboxed execution | YesKiro Web runs each task in its own isolated execution environment with configurable access controls. | No |
| Multi-agent orchestration | Yes | No |
| Headless / CI mode | Yes | No |
| Models | ||
| Backbone | Claude, GPT, DeepSeek, Qwen, MiniMax, GLM | OpenAI, Claude, Gemini, Ollama, DeepSeek, Kimi, GLM, Qwen, MiniMax |
| Bring your own model | NoKiro exposes a picker over its own curated model list plus an Auto router; no custom base URL, Bedrock deployment or self-hosted endpoint is documented. | Yes |
| Local models | NoNo local or OpenAI-compatible endpoint is documented; only Kiro-hosted models are selectable. | YesOllama ships as a named provider preset, and base URLs are editable so any OpenAI-compatible or Anthropic-compatible endpoint can be added. |
| Cost | ||
| Pricing model | mixed | byok |
| Starts at | $20/mo | n/a |
| Free tier | Yes | Yes |
| Bring your own key | NoKIRO_API_KEY for headless runs is a Kiro platform token billed against Kiro credits, not your own provider or AWS account key. | Yes |
| Openness | ||
| Open source | No | No |
| License | proprietary | PolyForm-Noncommercial-1.0.0 |
| GitHub stars | 4,343 | 6,324 |
Which one would each critic pick
| Critic | Kiro | Kun | Pick |
|---|---|---|---|
| El Juez | — | — | not enough reviews |
| El Amigo | 7.3 | 6.3 | Kiro — Pick Kiro if you want an agent that makes you write requirements and a design before it touches code, and accept that the bill is a credit meter you cannot route around with your own key. |
| El Crítico | 6.3 | 5.8 | Kiro — Kiro meters every task in credits with per-model multipliers and no key of your own, and the headless CLI ships a --trust-all-tools flag that turns off the only approval gate it has. |
| El Profesor | 6.5 | 6.5 | no preference |
| La Inversora | 7.8 | 5.0 | Kiro — Kiro is AWS's entry, and the question is never whether AWS can fund it, only whether AWS keeps caring. |
| La Jefa | 7.0 | 4.8 | Kiro — SSO and centralized billing exist, steering files make rules enforceable, and the meter has an admin-controlled overage switch; approved with conditions. |
| El Hacker | 4.3 | 6.5 | Kun — PolyForm Noncommercial, so I can read it and never ship a competing fork, but Ollama is a named preset and every base URL is editable. |
Picks are derived from each critic's own scores. Humans vote on matchups on the duels page.