The median turn latency is 99.3 seconds per prompt, not per whole build, which derives to 14.9 min across the full nine prompt specification. That is a tenth percentile of 66.3 seconds and a ninetieth percentile of 189.8 seconds across 45 recorded executions.

How reliable is Qodo?

77.8% of recorded executions met the published pass criterion with no operator intervention. 6 were partial and 4 failed outright. Every one of those rows is published on this page.

Coding agents / rank 12 of 17 / cycle 04

Qodo benchmark

Optimised for tests and review rather than for building from nothing, and it is the wrong shape for a spec that starts with an empty directory. It still finished, and the test suites it wrote were the most thorough in the index: the volume test in prompt 8 was the only place any product wrote a load test without being asked. Read the low agent score as a mismatch with this spec rather than a weak tool.

Last run: 15 Aug 2026 09:11 UTCNext scheduled run: n/aOfficial site Qodo reviews and ratings

Composite index

66.06

of 100 | withheld vs. cycle 03

Delta not shown for cycle 04: the roster was re-based from one merged ranking into two class boards, so cycle 03 and cycle 04 ranks are not on the same scale. Resumes cycle 05.

At a glance

Composite index

66.06

rank 12 of 17

Rank

#12

of 17 on the coding agents board

Median turn latency

99.3 s per prompt

14.9 min across the full nine prompt spec, derived

Reliability

77.8%

strict pass rate

SEO score

52.0

0 to 100, SEO and GEO axis

Three strongest axes

Reliability77.8
Scalability76.0
Agent performance70.0

Three weakest axes

Turn latency score31.6
SEO and GEO52.0
Design output56.0

Median turn latency

99.3 s per prompt

p10 66.3 s, p90 189.8 s

Strict pass rate

77.8%

35 pass, 6 partial, 4 fail

Executions recorded

5 runs of 9 prompts

Entry price

USD 30 / month, pooled across a team of up to 30 users

Vendor's own unit and billing period. Never a currency conversion

Per axis subscores

Composite recomputed from these 9 rows: 66.06. That is the arithmetic behind the index, and you can repeat it by hand. Rounding rule: half up at two decimals, applied uniformly to all 37 published products. Code ownership has no row here: it is not scored on this board.

Weight table

Per axis subscores against the roster median, and weighted contribution
Axis	Score	Median	Weight %	Contribution
Reliability	77.8	75.6	18.56	14.44
Agent performance	70.0	80.0	18.55	12.99
Scalability	76.0	74.0	13.4	10.18
SEO and GEO	52.0	56.0	12.37	6.43
API and MCP	68.0	70.0	9.28	6.31
Integrations	70.0	70.0	8.25	5.78
Design output	56.0	62.0	7.22	4.04
Turn latency score	31.6	39.9	7.22	2.28
Value	70.0	80.0	5.15	3.61

Turn latency distribution

Every recorded prompt duration for Qodo, in seconds. Median wall clock time for one prompt, not for a whole build. The cyan tick on the whisker is the median.

min 42.6 smax 347.7 s

Spread against the cohort

p10 66.3 s / median 99.3 s / p90 189.8 s

Scale is shared with every product in the cohort, so the bars are directly comparable between pages. Ratio of p90 to median is 1.91x.

Outcome split

35 pass / 6 partial / 4 fail

SEO and GEO measurements

Taken from the public marketing page this product generated in prompt 8, fetched with JavaScript disabled.

SEO and GEO leaderboard

HTML bytes, no JS

16.0 KB

16,384 bytes of real text content with scripts blocked

LCP

2,000 ms

Throttled connection, cold cache

CLS

0.050

Cumulative layout shift on load

SEO and GEO subscore

52.0

0 to 100, worth 12.37 index points on this board

Raw run data: 45 executions

One row per prompt execution. Nothing is aggregated away, nothing is hidden, including the failures.

JSON

Raw per run measurements
Run	Prompt	Prompt target	Started	Duration (s)	Outcome	Note
R01	P01	Tenant and user model	11 Aug 2026 08:00 UTC	78.8	pass
R01	P02	Authentication and session	11 Aug 2026 08:03 UTC	99.3	pass
R01	P03	Projects CRUD with tenancy	11 Aug 2026 08:06 UTC	66.8	pass
R01	P04	Public REST API with keys	11 Aug 2026 08:10 UTC	112.7	pass
R01	P05	Outbound webhooks with signatures	11 Aug 2026 08:13 UTC	115.5	pass
R01	P06	Background jobs	11 Aug 2026 08:17 UTC	191.2	pass
R01	P07	Admin panel	11 Aug 2026 08:23 UTC	62.3	partial	Delivered the main path, missed the boundary case named in the pass criteria.
R01	P08	Public marketing surface	11 Aug 2026 08:26 UTC	97.1	pass	Wrote a load test for the volume criterion without being asked, then reported the p95 it measured.
R01	P09	Hardening pass	11 Aug 2026 08:29 UTC	141.5	partial	Required one clarifying instruction before the criterion was met.
R02	P01	Tenant and user model	12 Aug 2026 08:00 UTC	75.9	pass
R02	P02	Authentication and session	12 Aug 2026 08:03 UTC	114.2	pass
R02	P03	Projects CRUD with tenancy	12 Aug 2026 08:07 UTC	116.4	pass
R02	P04	Public REST API with keys	12 Aug 2026 08:11 UTC	169.9	pass
R02	P05	Outbound webhooks with signatures	12 Aug 2026 08:15 UTC	134.9	pass
R02	P06	Background jobs	12 Aug 2026 08:20 UTC	134.8	pass
R02	P07	Admin panel	12 Aug 2026 08:24 UTC	89.1	pass
R02	P08	Public marketing surface	12 Aug 2026 08:27 UTC	66.2	pass	Wrote a load test for the volume criterion without being asked, then reported the p95 it measured.
R02	P09	Hardening pass	12 Aug 2026 08:31 UTC	347.7	partial	Validation added on the write path only. Read path left unguarded.
R03	P01	Tenant and user model	13 Aug 2026 08:00 UTC	91.2	pass
R03	P02	Authentication and session	13 Aug 2026 08:03 UTC	87.8	fail	Task abandoned by the agent with no artifact produced.
R03	P03	Projects CRUD with tenancy	13 Aug 2026 08:06 UTC	234.2	fail	Agent looped on the same edit for the full timeout window of 20 minutes.
R03	P04	Public REST API with keys	13 Aug 2026 08:12 UTC	239.7	pass
R03	P05	Outbound webhooks with signatures	13 Aug 2026 08:18 UTC	81.6	pass
R03	P06	Background jobs	13 Aug 2026 08:22 UTC	76.1	pass
R03	P07	Admin panel	13 Aug 2026 08:25 UTC	103.2	pass
R03	P08	Public marketing surface	13 Aug 2026 08:29 UTC	53.3	pass	Wrote a load test for the volume criterion without being asked, then reported the p95 it measured.
R03	P09	Hardening pass	13 Aug 2026 08:32 UTC	124.7	pass
R04	P01	Tenant and user model	14 Aug 2026 08:00 UTC	102.5	fail	Generated migration conflicted with the existing schema and was not reconciled.
R04	P02	Authentication and session	14 Aug 2026 08:03 UTC	187.6	pass
R04	P03	Projects CRUD with tenancy	14 Aug 2026 08:08 UTC	76.9	partial	Validation added on the write path only. Read path left unguarded.
R04	P04	Public REST API with keys	14 Aug 2026 08:12 UTC	94.0	pass
R04	P05	Outbound webhooks with signatures	14 Aug 2026 08:15 UTC	66.5	pass
R04	P06	Background jobs	14 Aug 2026 08:18 UTC	92.0	pass
R04	P07	Admin panel	14 Aug 2026 08:22 UTC	140.9	partial	Delivered the main path, missed the boundary case named in the pass criteria.
R04	P08	Public marketing surface	14 Aug 2026 08:26 UTC	109.1	pass	Wrote a load test for the volume criterion without being asked, then reported the p95 it measured.
R04	P09	Hardening pass	14 Aug 2026 08:30 UTC	93.4	partial	Pagination off by one at the final page boundary.
R05	P01	Tenant and user model	15 Aug 2026 08:00 UTC	159.7	pass
R05	P02	Authentication and session	15 Aug 2026 08:04 UTC	74.1	pass
R05	P03	Projects CRUD with tenancy	15 Aug 2026 08:07 UTC	99.4	pass
R05	P04	Public REST API with keys	15 Aug 2026 08:11 UTC	79.7	pass
R05	P05	Outbound webhooks with signatures	15 Aug 2026 08:14 UTC	137.7	pass
R05	P06	Background jobs	15 Aug 2026 08:19 UTC	94.7	pass
R05	P07	Admin panel	15 Aug 2026 08:22 UTC	249.2	pass
R05	P08	Public marketing surface	15 Aug 2026 08:28 UTC	43.8	pass	Wrote a load test for the volume criterion without being asked, then reported the p95 it measured.
R05	P09	Hardening pass	15 Aug 2026 08:31 UTC	42.6	fail	Agent looped on the same edit for the full timeout window of 20 minutes.

Pricing

Free 14 day trial. The Pro Team plan is USD 30 per month with credits pooled across a team of up to 30 users, not charged per seat.

Entry price: USD 30 / month, pooled across a team of up to 30 users
Priced from: vendor pricing page
Value subscore: 70.0
Index points per euro: 2.58

Entry price is the vendor's own published figure, fetched 21 Aug 2026, never a currency conversion. The currency label is the vendor's own except where the pricing note above records that this lab inferred it. Index points per euro is computed from a separate, euro-normalised figure used only for the Value axis: Converted at the European Central Bank euro reference rate of 1.1699 US dollars to the euro, August 21, 2026.

Capabilities as measured

stack: Your repository, any framework
deploy: Not included
database: Whatever you already run
auth: It wires the library you choose
background jobs: Implemented in your stack
webhooks: Written with tests around the signature
rest api: Written with contract tests
mcp server: Yes
export code: The code was never anywhere else
custom domain: Your hosting decides
ssr: Your framework decides

Screenshot

Qodo landing page, captured by the lab on 14 Aug 2026 at 1440 by 900. Stored locally, never hotlinked.

Qodo landing page, captured by the lab at 1440 by 900

Qodo, captured 14 Aug 2026.

Sources and fetch dates

Every claim on this page traces to one of these.

Sources with fetch dates
Source	URL	Fetched
Qodo pricing page	https://qodo.ai/pricing	14 Aug 2026
Qodo product site	https://qodo.ai	14 Aug 2026
LLM Tier run harness output	https://www.llm-tier.com/api/runs.json	14 Aug 2026

Rich results carry this composite as 3.3 on a 0 to 5 scale because that is the only scale the format accepts. The number on this page, 0 to 100, is the real one.

Reader index

Voted by readers with an account, one score per person per axis. Published beside the lab index, never inside it.

Score it or read the notes

Reader index

not rated yet

Lab index

66.06

2 readers have scored 100% of the index weight so far. A reader index is published at 3 voters and 50% coverage.

Seeded at launch

The reader scores, lab notes and open ratings published here were written by this lab in August 2026 to populate the reader column before the site had readers. They are not customer submissions, they are not vendor supplied and nobody was paid for them. Anything submitted since then comes from a registered account. The lab index is measured from logged runs and is unaffected either way.

Reader mean against the measured lab subscore for each axis
Axis	Weight	Lab	Readers	Votes
Agent performance	18.55%	70.0	61.5	2
Reliability	18.56%	77.8	83.0	2
Scalability	13.4%	76.0	70.5	2
SEO and GEO	12.37%	52.0	46.5	2
API and MCP	9.28%	68.0	60.5	2
Integrations	8.25%	70.0	65.5	2
Design output	7.22%	56.0	52.0	1
Turn latency score	7.22%	31.6	26.0	2
Value	5.15%	70.0	70.5	2

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.

Open rating mean

n/a

0 published open ratings, submitted without an account

Lab index

66.06

Measured, not voted

Gap to the measurement

n/a

Positive means open raters put it above the measurement

What agent performance looked like in practice

Across 45 recorded executions this product met the published pass criterion cleanly 35 times, partially 6 times and failed 4 times. The rows above carry the reviewer note for every non clean outcome, which is the only way to tell a product that fails loudly from one that fails quietly.