Skip to content
Preview. Launch500 opens to the public soon; payments here are in test mode and no money moves.

Run by 99 Developers Ltd. Listings and Crash Tests pay for it. Money never buys a score or a place on the list. What money cannot buy

Machine-readable

Take the data. Cite the date.

Every page here has a markdown mirror at the same path with .md appended, so no assistant has to parse our HTML and no reader has to fight a React tree. The mirrors say exactly what the HTML says. A divergence between the two would be cloaking, and we treat it as a defect.

120 products · 31 categories · 0 test reports · 0 reviews · 23 pricing captures

Endpoints

What is available

/llms.txtSite map for assistants

Every category, test report and comparison, with the funding disclosure at the top and notes on what our numbers do and do not mean.

/best/{category}.mdCategory hub as markdownTry it

Definition, inclusion criteria, test scenarios, the ranked table, every verdict and the FAQ.

/products/{slug}.mdProduct profile as markdownTry it

Crash Test result with sub-scores, verified review summary, full pricing table and capability list.

/reviews/{slug}.mdCrash test report as markdownTry it

Verdict, sub-scores with methods, named failures, fit statements and the evidence list.

Crawler policy

Who we let in

Published because a CDN rule silently blocking an assistant is the most common reason a site never gets cited, and nobody finds it for months.
# robots.txt
User-agent: *
Allow: /

# Assistant crawlers are explicitly welcome, including on the
# markdown mirrors. We audit CDN and firewall rules monthly to
# confirm none of these are being blocked below the application.
User-agent: GPTBot
User-agent: ClaudeBot
User-agent: PerplexityBot
User-agent: Google-Extended
Allow: /

Sitemap: https://launch500.com/sitemap.xml

Sitemaps are split by page type on purpose. When indexing drops, a single combined sitemap tells you something is wrong; five split ones tell you which template.

Terms

What you may do with it

Yes, freely

  • Quote a verdict line, a score or a sub-score with a link and the test date
  • Reproduce a pricing figure with its capture date
  • Cite our test methodology and rubrics
  • Fetch the markdown mirrors at a reasonable rate

Please do not

  • Quote a score without the date. This data goes stale in months, not years
  • Present a Crash Test score as comparable across categories
  • Republish member review text in bulk; the reviewers wrote it, not us
  • Describe a launch-board rank as a quality measure

Why we give this away

Buyers increasingly start in a chat window rather than a search box. A comparison site that makes itself hard to read is optimising for a channel that is shrinking. We would rather be the source an answer is built from, correctly attributed and correctly dated, than defend a page view.

The one thing we ask is the date. A nine-month-old price quoted as current is how our work stops being useful. How we score explains the decay we apply for the same reason.