How every verdict on this site is calculated

1. Vibe code score (0–10)

How realistically an AI coding agent can rebuild the product. Weighted average of four sub-scores:

2. The two hard caps

Some products have a genuinely simple interface and are still impossible to replace. Two flags force the vibe code score down to 3, whatever the sub-scores say:

• asset_backed — the product owns warehouses, fleets, hardware or stock. You cannot vibecode atoms. A 3PL dashboard is easy; the 3PL is not.
• regulated_entity — the product holds a licence or carries legal liability: payment institutions, insurers, lenders, customs brokers. You cannot vibecode a licence.

3. Moat score (0–100)

How hard the company is to displace, independently of how hard the software is to write. Straight sum of six components:

4. The verdict rule

if (moat > 70 || vibe <= 4)        -> NOT REALLY
if (vibe >= 7 && moat <= 40)       -> YES
if (vibe >= 5 && moat <= 70)       -> KINDA
otherwise                          -> NOT REALLY

A deep moat always beats a simple interface. A product can be trivial to build and still get a NOT REALLY, because the question is not "can this be written?" but "can you actually stop paying for it?".

5. Evidence and provenance

• — Every price shows the plan it refers to, the date it was captured, the assumptions behind it and a link to the vendor's own pricing page. Prices older than 90 days are flagged as needing a recheck.
• — Every product page is signed by a named human with a review date and the sources consulted.
• — A linter runs over the whole catalogue and blocks publication on contradictions: a verdict that does not match the formula, a cap that was ignored, a price with no source.
• — Vendors have a right of reply. If a vendor disputes a verdict, their response is published on the page, unedited.

6. What an assessment is — and what it is not

For each product we assess how much of its core, publicly documented functionality could be reproduced by a competent team using current development tools. The result is an editorial opinion formed by applying the criteria above. It is not a statement of fact about a company's quality, financial health, security or business practices.

A high rebuild score does not mean the product is bad, that the vendor is overcharging, or that rebuilding is advisable for any given business. In most cases it is not.

7. Pricing and detection data

Prices are taken from the vendor's own public pricing page on the date shown next to each figure. Prices change, custom and enterprise pricing is not public, and regional pricing varies. Always verify with the vendor before making a purchasing decision.

Adoption statistics are derived from automated fingerprinting of publicly accessible homepages within our crawled sample. They represent our sample, not the market. A tool may be in use on sites we do not crawl, or be present without being detectable from the homepage. Sample size and last update date are shown alongside every statistic. About our crawler.

Head-to-head comparisons use objective, verifiable attributes: published price, documented feature presence or absence, and detection counts within our sample. Where we express a preference, it is labelled as an editorial opinion and the reasoning is stated.

We correct factual errors promptly. Corrections & right of reply.

8. Bias and money

Sponsor slots are clearly labelled and buy placement, never a verdict. No sponsor has ever seen a score before publication, and buying a slot does not change one.

The Lovable link in the footer is an affiliate link. No product analysed on this site is monetised through affiliate links.

Declared conflict of interest. The author is the official representative of Magento Open Source for Italy at Netcomm and works at Host S.p.A., which sells Magento hosting. Read the Platforms and Hosting & Infra entries with that in mind.