Head to head / curated pair / cycle 04
Mocha vs Trickle
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.
Good at small internal tools and honest about it. Under this specification the multi tenant boundary leaked in 2 of 5 runs during the prompt 3 cross tenant read test, which is the single most serious defect we recorded in this cohort.
The best public page output in the lower half, with real server rendered text and clean metadata, which lifts its SEO subscore well above its neighbours. Everything behind the marketing surface is thin: no key management, no signed webhooks and no durable background work.
Index gap
0.22
Mocha leads
Axes won
6 / 4
Mocha versus Trickle, of ten axes
Faster median
Trickle
87.0 s per prompt
Higher pass rate
Mocha
53.3%
Every measurement, side by side
Cyan marks the better figure on each row. The delta column is the first product minus the second.
| Measurement | Mocha | Trickle | Delta |
|---|---|---|---|
| Composite index | 55.67 | 55.45 | +0.22 |
| Agent performance (weight 18) | 66.0 | 62.0 | +4.00 |
| Reliability (weight 18) | 53.3 | 51.1 | +2.20 |
| Scalability (weight 13) | 55.0 | 52.0 | +3.00 |
| SEO and GEO (weight 12) | 55.0 | 63.0 | -8.00 |
| API and MCP (weight 9) | 44.0 | 41.0 | +3.00 |
| Integrations (weight 8) | 52.0 | 49.0 | +3.00 |
| Design output (weight 7) | 72.0 | 79.0 | -7.00 |
| Speed (weight 7) | 29.8 | 36.1 | -6.30 |
| Value (weight 5) | 74.0 | 75.0 | -1.00 |
| Code ownership (weight 3) | 50.0 | 45.0 | +5.00 |
| Median seconds per prompt | 105.2 | 87.0 | +18.20 |
| p10 seconds | 61.1 | 49.4 | +11.70 |
| p90 seconds | 186.8 | 137.1 | +49.70 |
| Executions failed | 9 | 11 | -2.00 |
| HTML bytes, no JS | 6.0 KB | 15.0 KB | -9216.00 |
| LCP milliseconds | 3,040 | 2,260 | +780.00 |
| CLS | 0.130 | 0.070 | +0.06 |
| Entry price EUR | 20.00 | 15.00 | +5.00 |
Screenshot diff
Both landing pages, captured by the lab on 14 Aug 2026 at 1440 by 900. Stored locally, never hotlinked.
Mocha, captured 14 Aug 2026.
Trickle, captured 14 Aug 2026.
Speed spread on a shared scale
Mocha
61.1 / 105.2 / 186.8 seconds
Trickle
49.4 / 87.0 / 137.1 seconds
Axis by axis, who wins
Mocha wins 6 of 10
- Agent performance66.0
- Reliability53.3
- Scalability55.0
- API and MCP44.0
- Integrations52.0
- Code ownership50.0
Trickle wins 4 of 10
- SEO and GEO63.0
- Design output79.0
- Speed36.1
- Value75.0
Verdict
Mocha takes the composite by 0.22 points. That is inside the noise of a five run sample, so the correct conclusion is that these two are tied on the composite and the choice should come down to a single axis you care about.
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.