Opinion page / measured product / rank 8
v0 Reviews and Ratings (2026)
Reader ratings for v0, aggregated on the same 0 to 100 scale we use for the lab index, with our own commentary underneath. If you are looking for v0 opiniones, reviews or a rating you can check, the measurements behind every claim are on the v0 benchmark page.
Reader index
80.68
6 voters, 54 axis scores. Never blended into the lab index.
Lab index
74.69
Measured on the vibeOps spec
Strict pass rate
84.4%
38 clean and 1 failed executions
Median per prompt
65.2 s
p90 104.1 s
Reader index
One score per reader per axis on a 0 to 100 scale, editable at any time.
Reader index
80.68
Lab index
74.69
6 readers, 54 axis scores, last change 14 Aug 2026. Readers rate v0 6.0 points above the measurement.
| Axis | Weight | Lab | Readers | Votes | Reader mean |
|---|---|---|---|---|---|
| Agent performance | 18% | 80.0 | 85.2 | 6 | |
| Reliability | 18% | 84.4 | 88.5 | 6 | |
| Scalability | 13% | 72.0 | 81.6 | 5 | |
| SEO and GEO | 12% | 76.0 | 85.7 | 6 | |
| API and MCP | 9% | 60.0 | 56.8 | 4 | |
| Integrations | 8% | 66.0 | 76.2 | 6 | |
| Design output | 7% | 94.0 | 100.0 | 5 | |
| Speed | 7% | 48.2 | 53.7 | 6 | |
| Value | 5% | 68.0 | 75.5 | 6 | |
| Code ownership | 3% | 86.0 | 93.3 | 4 |
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 v0
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 v0
Written by readers with an account. Sorted by upvotes, then by date.
No reader lab notes yet. A note has to describe something you actually built, so the first one here is worth reading.
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 | 1 | |
| 70 to 79 | 1 | |
| 60 to 69 | 0 | |
| 0 to 59 | 0 |
Lab commentary
Our reading of the numbers, kept separate from the reader ratings.
Fastest median in the cohort and the highest blind design score by a clear margin. The weakness is operational: background jobs in prompt 6 were implemented as fire and forget route handlers in 4 of 5 runs, which is not a queue, and the admin panel needed manual work on staff gating.
On the measured axes, v0 is strongest at design output with a subscore of 94.0 and weakest at speed at 48.2. Because speed carries 7 of the 100 index points, that weakness costs it roughly 3.63 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.
2 open ratings
Newest first, no account needed. Moderated for spam and vendor astroturfing, not for sentiment.
Backend needs you to drive
Nikhil Rao, Full stack developer | 08 Aug 2026
71The generated route handlers are fine but you are writing the operational layer yourself.
Unmatched for interface work
Sara Delgado, Design engineer | 03 Aug 2026
88If the job is the front end, nothing else is close. If the job is a queue, look elsewhere.
Add an open rating
No account needed. For a score that counts toward the reader index, use the axis form above.