Head to head / curated pair / cycle 04
Dyad vs bolt.diy
Both products were given the identical 9 prompt vibeOps specification, 5 times each. Nothing on this page is an impression, all of it is a measurement from the same harness.
Runs on your own machine against your own model key, which makes it one of the cheapest routes through the spec and gives it a code ownership score that hosted products cannot match: there is no platform to leave. The trade is variance, since throughput depends on the key you point it at, and there is no managed runtime to catch a bad deploy.
The community built sibling of a commercial product, and the gap between them is the point of measuring it: same interaction model, noticeably less polish in the agent loop. It has one of the widest p10 to p90 spreads in the index, because a run that picks up the wrong model configuration behaves nothing like one that does not. Worth the entry for anyone who needs the whole stack under their own control.
Index gap
6.60
Dyad leads
Axes won
8 / 1
Dyad versus bolt.diy, of ten axes
Faster median
Dyad
83.8 s per prompt
Higher pass rate
bolt.diy
55.6%
Every measurement, side by side
Cyan marks the better figure on each row. The delta column is the first product minus the second.
| Measurement | Dyad | bolt.diy | Delta |
|---|---|---|---|
| Composite index | 64.77 | 58.17 | +6.60 |
| Agent performance (weight 18) | 68.0 | 60.0 | +8.00 |
| Reliability (weight 18) | 55.6 | 55.6 | +0.00 |
| Scalability (weight 13) | 64.0 | 52.0 | +12.00 |
| SEO and GEO (weight 12) | 72.0 | 62.0 | +10.00 |
| API and MCP (weight 9) | 60.0 | 48.0 | +12.00 |
| Integrations (weight 8) | 62.0 | 54.0 | +8.00 |
| Design output (weight 7) | 72.0 | 74.0 | -2.00 |
| Speed (weight 7) | 37.5 | 27.6 | +9.90 |
| Value (weight 5) | 92.0 | 90.0 | +2.00 |
| Code ownership (weight 3) | 98.0 | 97.0 | +1.00 |
| Median seconds per prompt | 83.8 | 113.8 | -30.00 |
| p10 seconds | 54.4 | 59.6 | -5.20 |
| p90 seconds | 149.9 | 231.5 | -81.60 |
| Executions failed | 10 | 10 | +0.00 |
| HTML bytes, no JS | 20.0 KB | 15.0 KB | +5120.00 |
| LCP milliseconds | 1,880 | 2,320 | -440.00 |
| CLS | 0.040 | 0.080 | -0.04 |
| Entry price EUR | 0.00 | 0.00 | +0.00 |
Screenshot diff
Both landing pages, captured by the lab on 14 Aug 2026 at 1440 by 900. Stored locally, never hotlinked.
Dyad, captured 14 Aug 2026.
bolt.diy, captured 14 Aug 2026.
Speed spread on a shared scale
Dyad
54.4 / 83.8 / 149.9 seconds
bolt.diy
59.6 / 113.8 / 231.5 seconds
Axis by axis, who wins
Dyad wins 8 of 10
- Agent performance68.0
- Scalability64.0
- SEO and GEO72.0
- API and MCP60.0
- Integrations62.0
- Speed37.5
- Value92.0
- Code ownership98.0
bolt.diy wins 1 of 10
- Design output74.0
Verdict
Dyad takes the composite by 6.60 points. It wins on the weighted total, but the axis table is where the real decision sits: Dyad takes 8 axes and bolt.diy takes 1.
If the work in front of you is mostly interface, weight the design and speed rows. If it is a product with an API, webhooks and background jobs, weight agent performance, reliability and the API and MCP row, which together carry 45 of the 100 index points. If the project has to outlive its vendor, read the code ownership row first and treat everything else as secondary.
Both products in this comparison were measured in the same cycle, on the same specification, by the same harness. The per run data for each is on its product page and in /api/runs.json.