About BuilderProof

Contributors

Benchmarks, methodology, and write-ups are produced and maintained by the BuilderProof editorial team. We attribute work to the team rather than to invented individuals, and contributors are named only when they contribute real, verifiable work to a result.

Editorial-independence policy

Every score is produced by a published, version-stamped method, not by editorial preference. The scoring rubric, the per-axis weights, and the fixed test brief are documented in public on our methodology page before any builder is scored. When two reviewers grade the same axis, disagreements beyond a set threshold are reconciled against the rubric before a sub-score is published. When the methodology updates, every builder is re-run together so results stay comparable across a benchmark generation.

Conflict-of-interest disclosure: BuilderProof is operated by Totalum, and Totalum is one of the builders scored here. To keep that relationship from shaping outcomes, Totalum is scored with the exact same rubric as every other builder, has no veto over any score, and does not set the score weights. The current data shows this in practice: Totalum leads on whitelabel, code ownership, EU residency, and the API/MCP surface, but it does not win on build speed, relational SQL support, or brand mindshare, where other builders rank higher. No builder, including the operator, is ranked first across every category.

How to challenge a score: if you believe a result is wrong or out of date, send the evidence through our contact form. We review every challenge against the published method, and a correction that holds up is applied in the next cycle with the prior figure retained in the page history.