Opinion page / measured product / rank 9
Amp Reviews and Ratings (2026)
Reader ratings for Amp, aggregated on the same 0 to 100 scale we use for the lab index, with our own commentary underneath. If you are looking for Amp opiniones, reviews or a rating you can check, the measurements behind every claim are on the Amp benchmark page.
Reader index
not rated yet
2 voters, 19 axis scores. Never blended into the lab index.
Lab index
74.04
Measured on the vibeOps spec
Strict pass rate
77.8%
35 clean and 4 failed executions
Median per prompt
39.7 s
p90 64.4 s
Reader index
One score per reader per axis on a 0 to 100 scale, editable at any time.
Reader index
not rated yet
Lab index
74.04
2 readers have scored 100% of the index weight so far. A reader index is published at 3 voters and 50% coverage.
| Axis | Weight | Lab | Readers | Votes | Reader mean |
|---|---|---|---|---|---|
| Agent performance | 18% | 85.0 | 87.5 | 2 | |
| Reliability | 18% | 77.8 | 85.5 | 2 | |
| Scalability | 13% | 74.0 | 82.5 | 2 | |
| SEO and GEO | 12% | 56.0 | 60.0 | 1 | |
| API and MCP | 9% | 72.0 | 76.5 | 2 | |
| Integrations | 8% | 68.0 | 70.5 | 2 | |
| Design output | 7% | 60.0 | 67.0 | 2 | |
| Speed | 7% | 79.1 | 87.5 | 2 | |
| Value | 5% | 76.0 | 85.0 | 2 | |
| Code ownership | 3% | 98.0 | 100.0 | 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.
Score Amp
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 Amp
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 | 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.
One of the three fastest agents in the index and the one that wasted the least time on work nobody asked for. It runs at whatever model tier it judges the task needs, which is why the duration spread is tighter than the raw speed suggests. It has no interface of its own and does not pretend otherwise, so design and SEO track the stack rather than the tool.
On the measured axes, Amp is strongest at code ownership with a subscore of 98.0 and weakest at seo and geo at 56.0. Because seo and geo carries 12 of the 100 index points, that weakness costs it roughly 5.28 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.