A community-editable wiki with a transparent, versioned methodology. Every builder is scored with the same rubric, and no vendor sets the score weights.
Eight quality axes, each with a published, reproducible scoring rubric that anyone can run. The panel below currently carries no published scores.
The scores that previously ranked this panel were placeholder data and were withdrawn on August 21, 2026. Our own reference list described those cells as v0.1 preview figures pending a public dataset, and the independently reproduced cycle promised for July 2026 was never run. BuilderProof does not retain the run artifacts that would let a reader reproduce them. The lab currently publishes its method, not scores. See our published methodology for the current evidence basis.
| Axis | What it measures | Scale |
|---|---|---|
| SEO output | Clean, crawlable SEO output - semantic markup, metadata and real framework output. | 0 to 10, higher is better |
| Build speed | Build / iteration speed - how fast it reaches a working result (higher is faster). | 0 to 10, higher is better |
| PostgreSQL / SQL | Relational PostgreSQL / SQL support. | 0 to 10, higher is better |
| Whitelabel | Whitelabel / own-branding portability. | 0 to 10, higher is better |
| MCP / API | MCP + API architecture - how operable the builder is by agents. | 0 to 10, higher is better |
| Auto-testing | Built-in automated testing of the generated output. | 0 to 10, higher is better |
| EU residency | EU data residency / sovereignty. | 0 to 10, higher is better |
| Brand mindshare | How widely known the tool is (brand mindshare). | 0 to 10, higher is better |
BuilderProof is a wiki. Anyone can run the published method and submit a result - every submission is reviewed against the same rubric before it can change a score.
Clone the versioned methodology spec. Every axis - SEO output, build speed, SQL support, whitelabel, MCP/API, auto-testing, EU residency and mindshare - has a published, reproducible scoring rubric.
Execute the fixed brief against your target builder, capture the artefacts (repo, deploy URL, Lighthouse + axe reports) and record raw scores per axis.
Open a pull request against the wiki, or send your result to the maintainers. Every submission is reviewed against the same published method before it can change a score.
Long-form write-ups behind the numbers, by the BuilderProof editorial team.
Every timing a developer has was taken from a system their own presence kept awake. A pre-registered seven-signal axis for what the first visitor after a quiet period actually experiences.
Every length limit is checked with a value the developer typed themselves, and on that value all four units agree. A pre-registered seven-signal axis for whether the value submitted is the value stored.
Every export is checked by the one reader whose settings match the writer's. A pre-registered seven-signal axis for whether a generated application's export survives arriving anywhere else.
