Opinion page / measured product / rank 6
Kiro Reviews and Ratings (2026)
Reader ratings for Kiro, aggregated on the same 0 to 100 scale we use for the lab index, with our own commentary underneath. If you are looking for Kiro opiniones, reviews or a rating you can check, the measurements behind every claim are on the Kiro benchmark page.
Reader index
78.57
3 voters, 28 axis scores. Never blended into the lab index.
Lab index
76.31
Measured on the vibeOps spec
Strict pass rate
93.3%
42 clean and 1 failed executions
Median per prompt
72.4 s
p90 140.4 s
Reader index
One score per reader per axis on a 0 to 100 scale, editable at any time.
Reader index
78.57
Lab index
76.31
3 readers, 28 axis scores, last change 14 Aug 2026. Readers rate Kiro 2.3 points above the measurement.
| Axis | Weight | Lab | Readers | Votes | Reader mean |
|---|---|---|---|---|---|
| Agent performance | 18% | 84.0 | 85.7 | 3 | |
| Reliability | 18% | 93.3 | 93.3 | 3 | |
| Scalability | 13% | 80.0 | 81.3 | 3 | |
| SEO and GEO | 12% | 60.0 | 65.0 | 3 | |
| API and MCP | 9% | 72.0 | 76.0 | 3 | |
| Integrations | 8% | 74.0 | 75.7 | 3 | |
| Design output | 7% | 65.0 | 67.5 | 2 | |
| Speed | 7% | 43.4 | 49.0 | 3 | |
| Value | 5% | 78.0 | 80.5 | 2 | |
| Code ownership | 3% | 97.0 | 96.7 | 3 |
The reader index is a weighted mean of reader submitted axis scores using the published index weights, renormalised over the axes readers have scored. It is never blended into the lab index. How this works.
Score Kiro
Your scores feed the reader column only. Submitting an axis again edits your existing score rather than adding a second vote.
Reader scores need an account so one person cannot vote twice. Create a reader account or sign in.
Reader scores are published in a separate reader index column. They never move the measured lab index.
Reader lab notes on Kiro
Written by readers with an account. Sorted by upvotes, then by date.
Writing the spec first is slower and I stopped minding
Ines Barros | 13 Aug 2026
We ran a bake off across four agents on a real feature, not on a benchmark. This one was consistently the slowest to first code and the fastest to a merged change, because the plan it wrote up front was reviewable before anything depended on it. Twice a reviewer caught a wrong assumption in the plan in about a minute, which would have been an hour of review on a finished diff. The published median puts it mid table on speed and I think that undersells it: the axis measures time per prompt and the thing that matters to us is time per merge.
Jide Okonkwo | 14 Aug 2026
Time per merge is the number I wish this site published. Understood why it does not, since it is not measurable without a team in the loop, but it is the one my week is made of.
Write a lab note
What you built, what broke, what you measured. Short opinions belong in the open rating form further down.
Open rating distribution
Open ratings submitted without an account. Neither the lab index nor the reader index is part of this average.
| Band | Share | Ratings |
|---|---|---|
| 90 to 100 | 0 | |
| 80 to 89 | 0 | |
| 70 to 79 | 0 | |
| 60 to 69 | 0 | |
| 0 to 59 | 0 |
Lab commentary
Our reading of the numbers, kept separate from the reader ratings.
Writes a specification and a task list before it writes code, which costs it roughly a third more wall clock than the fastest agents and buys back one of the tightest duration spreads in the index. The specification step is why prompt 2 came out correct in five of five runs: the tenancy rule was written down before anything depended on it.
On the measured axes, Kiro is strongest at code ownership with a subscore of 97.0 and weakest at speed at 43.4. Because speed carries 7 of the 100 index points, that weakness costs it roughly 3.96 points against a perfect result on that axis alone.
Reader ratings and lab measurements answer different questions. A reader rating carries the thing a harness cannot capture: whether the product was pleasant to work with over weeks, how support behaved, whether the bill matched the plan. The lab index carries the thing an opinion cannot: 45 timed executions of the same specification with the failures counted. Read them side by side and treat a large gap between the two as the interesting signal.
0 open ratings
Newest first, no account needed. Moderated for spam and vendor astroturfing, not for sentiment.
No reader ratings published yet. Yours would be the first.
Add an open rating
No account needed. For a score that counts toward the reader index, use the axis form above.