Methodology, corrections and data freshness

Methodology

• Every app entry links to a public source (a post, interview, case study or revenue page) that names the AI tool used to build it. Entries summarize that source in our own words.
• Revenue figures are copied as the maker or source published them, with the source date where one is given. We normalize to monthly USD only for sorting (MRR as stated, ARR/12). Savings, prizes and exits are labeled and not counted as revenue.
• Evidence tiers: A = processor-verified (for example Stripe via TrustMRR); B = documented (the linked source is a first-party case study by the build-tool maker, or shows the revenue dashboard); C = maker-claimed (everything else, including third-party lists that repeat a figure). Each app shows the basis for its tier and the date its source link was last checked (evidence_checked_at). Vibe Shipped does not audit revenue.
• Tool and harness prices are copied from official pricing pages, with the date we checked. Features are marked "Yes" only when official docs state them; "Not verified" means we could not confirm it, not that it is missing.
• Answer pages under /best are built only from this dataset. Counts are counts of our own listings, not market share.
• Submissions are reviewed by a person before going live. Listings and rankings are never paid for; sponsored placements are labeled.

Corrections policy

If an entry is wrong, out of date, or you want it removed, email vibeshipped@mail.grokbot.com with the page link and what should change. Include a public source for any new figure. We correct or remove entries rather than argue about them, and we log material changes on What's new with the date.

Data freshness

Computed from the live dataset at build time.

Full dataset: JSON · CSV (CC BY 4.0) · changelog API / RSS.