Provenance Record

Well-structured News piece (525 words, within the News 400-1200 range). Clear Overview / What We Know / What We Don't Know / Analysis structure. Appropriate technical depth and a fair 'What We Don't Know' section flagging self-reported, unaudited metrics.

Read all three gzipped snapshots from disk and verified every cited claim. source-0.html.gz (prnewswire, the press release, status 200): confirms $500M Series F at $10.5B post-money, GIC lead with verbatim investor list (Accel, Y Combinator, Craft, Felicis, Peak XV, Coatue), 600% YoY database increase, 250,000 customers, 'Claude Code is the largest contributor since the start of the year', 370% Supabase-for-Platforms growth, Multigres as 'an open source scaling layer for Postgres' (verbatim — the exact phrase appears in the release), and the boilerplate 'The majority of AI app builders and more than 9 million developers use Supabase.' source-1.html.gz (supabase.com blog, status 200): confirms Stripe second investment, Georgian and Salesforce Ventures as new investors, 60%+ of new databases launched by AI tools, and the verbatim fragment 'as Claude Code and Codex expand the number of people who can build.' source-2.html.gz (technode.global, status 200): confirms the $500M/$10.5B framing, GIC lead, seven months after Series E, >$1B total, founded 2020, and the AI-coding-agent demand framing.

All claims supported. The Copplestone quote 'Demand for Supabase is exploding...Agents are now deploying the majority of databases on our platform' is verbatim from the press release; the ellipsis honestly elides the middle two sentences and the attributed title 'Co-founder and CEO of Supabase' matches the release exactly. The '9 million developers' figure is attributed correctly and exclusively to the press release, which carries that exact wording ('more than 9 million developers'); the blog phrases it differently ('Nearly 10 million developers') and the article correctly does NOT use the blog for that number. No hallucinations detected.

High-quality, accurately sourced submission ready for publication. Verdict upgraded from the script's auto APPROVE_WITH_CORRECTIONS (triggered only by the allowlist warning) to APPROVE after full source verification confirmed no content errors requiring a public correction.