{
  "id": "jetbrains-junie-vs-kiro",
  "ids": [
    "jetbrains-junie",
    "kiro"
  ],
  "title": "JetBrains Junie vs Kiro: planning, development tools and model costs",
  "heading": "JetBrains Junie vs Kiro",
  "kicker": "AI coding tools comparison",
  "deck": "Compare Junie and Kiro for planned code changes, terminal and IDE adoption, provider connections and the difference between model charges and included credits.",
  "description": "Compare Junie and Kiro for planned code changes, terminal and IDE adoption, provider connections and the difference between model charges and included credits.",
  "answerHeading": "Which workflow fits your team?",
  "answer": "Consider Junie when its JetBrains-related tooling, terminal workflow and available model connections fit the project. Consider Kiro when its specification-led IDE or CLI workflow fits. Separate a free agent layer, a free model and a paid usage allowance before costing either approach.",
  "checkedAt": "2026-10-15",
  "researchTag": "Agent workflow, operating boundary and commercial scope",
  "researchLimit": "Official product and account terms reviewed. Exercises are proposed evaluation briefs, not completed product benchmarks or measured quality results.",
  "datasetDescription": "Seven buying differences, four proposed evaluation scenarios and four acceptance checks for JetBrains Junie vs Kiro.",
  "type": "workflow-buying",
  "rows": [
    [
      "Product approach",
      "JetBrains coding agent with structured planning",
      "AWS agent with specification-led development"
    ],
    [
      "Development surface",
      "Terminal and JetBrains-related workflows",
      "Kiro IDE and command-line workflows"
    ],
    [
      "Project guidance",
      "Guidelines, skills and plan files",
      "Specifications, project guidance and hooks"
    ],
    [
      "Model arrangement",
      "Lite, provider-key or JetBrains AI arrangements differ",
      "Available models and credit consumption depend on offer"
    ],
    [
      "Free scope",
      "Lite/free layer; provider usage may remain chargeable",
      "Limited credits and selected model access"
    ],
    [
      "Adoption check",
      "Confirm IDE, CLI and provider compatibility",
      "Confirm IDE, CLI and repository tooling"
    ],
    [
      "Cost brief",
      "Model provider, AI credits and any required IDE",
      "Plan credits, selected models and additional usage"
    ]
  ],
  "scenarios": [
    {
      "name": "Plan review",
      "question": "Can the owner redirect the plan before implementation?",
      "left": "Use the retained Junie planning workflow.",
      "right": "Use a Kiro requirement and design brief.",
      "note": "The agreed change and acceptance boundary are explicit before execution."
    },
    {
      "name": "Project navigation",
      "question": "Can the developer inspect the affected code with familiar tooling?",
      "left": "Check the selected JetBrains or terminal arrangement.",
      "right": "Check the chosen Kiro IDE or CLI arrangement.",
      "note": "Navigation, build and debugging needs remain practical."
    },
    {
      "name": "Model billing",
      "question": "Which account receives charges for an actual test task?",
      "left": "Record Lite, JetBrains credits or the provider key used.",
      "right": "Record the credit package and selected model.",
      "note": "The owner can distinguish subscription, provider and additional usage."
    },
    {
      "name": "Repeatable guidance",
      "question": "Can another developer reuse the project instructions?",
      "left": "Retain the proposed guidelines and plan with the project.",
      "right": "Retain specifications and relevant project instructions.",
      "note": "A follow-up task uses the same agreed conventions."
    }
  ],
  "exampleTable": {
    "caption": "Proposed evaluation in an authorised test repository. Record the actual tool version, account and evidence.",
    "headers": [
      "Requirement",
      "Proposed exercise",
      "Accept when"
    ],
    "rows": [
      [
        "Plan review",
        "Can the owner redirect the plan before implementation?",
        "The agreed change and acceptance boundary are explicit before execution."
      ],
      [
        "Project navigation",
        "Can the developer inspect the affected code with familiar tooling?",
        "Navigation, build and debugging needs remain practical."
      ],
      [
        "Model billing",
        "Which account receives charges for an actual test task?",
        "The owner can distinguish subscription, provider and additional usage."
      ],
      [
        "Repeatable guidance",
        "Can another developer reuse the project instructions?",
        "A follow-up task uses the same agreed conventions."
      ]
    ]
  },
  "sections": [
    {
      "id": "commercial-layer",
      "title": "Name the layer that is free",
      "navLabel": "Free access and models",
      "paragraphs": [
        "Junie’s current page distinguishes Lite, a free bring-your-own-key layer and JetBrains AI cloud-credit plans. A separately billed model key is still a cost even if the surrounding tool has no subscription fee.",
        "Kiro Free is a limited service allowance; paid credit packages and enterprise scope differ. Record the chosen model and account on both sides, then check the allowance that remains after representative work."
      ]
    },
    {
      "id": "maintainability",
      "title": "Evaluate a second change",
      "navLabel": "Project continuity",
      "paragraphs": [
        "After the first accepted change, ask a different developer to make a small related edit. Inspect how the retained plan and project guidance help them understand the code and intended behaviour.",
        "Keep the diff and review notes rather than scoring a single demonstration. This brief does not rank model quality, certify generated code or claim that either agent removes the need for an accountable maintainer."
      ]
    }
  ],
  "faqs": [
    {
      "question": "Does Junie bring-your-own-key mean free model inference?",
      "answer": "No. The agent layer and the model provider’s charges are separate. Junie Lite and JetBrains AI credits also have distinct scope."
    },
    {
      "question": "Does Kiro Free include every paid capability?",
      "answer": "No. Credits, models and organisation features depend on the selected offer and account conditions."
    },
    {
      "question": "Which should a JetBrains team choose?",
      "answer": "Start with required IDE and language workflows, then compare one planned change and a second-person review. Brand familiarity alone does not establish fit."
    }
  ],
  "sources": [
    {
      "url": "https://junie.jetbrains.com/",
      "facts": "Current product workflow, account or commercial boundaries; buyer exercises are editorial proposals."
    },
    {
      "url": "https://junie.jetbrains.com/docs/",
      "facts": "Current product workflow, account or commercial boundaries; buyer exercises are editorial proposals."
    },
    {
      "url": "https://kiro.dev/",
      "facts": "Current product workflow, account or commercial boundaries; buyer exercises are editorial proposals."
    },
    {
      "url": "https://kiro.dev/pricing/",
      "facts": "Current product workflow, account or commercial boundaries; buyer exercises are editorial proposals."
    },
    {
      "url": "https://kiro.dev/docs/",
      "facts": "Current product workflow, account or commercial boundaries; buyer exercises are editorial proposals."
    }
  ],
  "relatedLinks": [
    {
      "path": "/categories/ai-coding-assistants/",
      "title": "Explore AI coding assistants"
    },
    {
      "path": "/guides/ai-coding-agent-evaluation-checklist/",
      "title": "Build an AI coding agent evaluation brief"
    }
  ],
  "downloads": [
    {
      "path": "/downloads/jetbrains-junie-vs-kiro-evaluation.csv",
      "title": "Download the coding-agent evaluation checklist (CSV)",
      "description": "Four proposed exercises with blank evidence, retained account, outcome and owner fields."
    }
  ]
}