Supabase as Default Backend for AI Apps

Supabase is turning AI app generation into infrastructure revenue, because the assistant that creates an app also chooses the default database, auth, and storage stack. Once Bolt.new or Lovable wires Supabase into a project, revenue grows when that app gets real users, stores more files, and runs a larger database. That makes Supabase less like a one time developer tool sale and more like a metered utility attached to app usage.

• The key advantage is distribution inside the creation workflow. Bolt.new and Lovable became default front doors for non technical users building full stack apps, and Supabase was the easiest backend they could provision automatically, which helped push Supabase from about $30M ARR at the end of 2024 to $70M by August or September 2025.
  1 sacra 2 sacra 4 sacra 5 sacra
• This monetizes differently from the app builders themselves. Bolt, Lovable, and Cursor mainly charge for prompts, chats, or seats during creation and editing. Supabase gets paid later, when a shipped app accumulates MAUs, storage, bandwidth, and database usage. That usually means higher retention because an app that stays live keeps consuming backend resources.
  2 sacra 3 sacra 4 sacra 5 sacra
• The tradeoff is that partners are becoming competitors. Bolt Cloud and Lovable Cloud are adding platform native backend products so they can capture recurring infrastructure revenue themselves, while PlanetScale and Neon compete for the database layer with more specialized products and graduation paths for larger workloads.
  1 sacra 2 sacra 4 sacra 5 sacra

The next phase is a fight over who owns the default backend for AI built software. If Supabase keeps winning the automatic provisioning slot, it can compound with every new wave of generated apps. If app builders keep moving backend services in house, Supabase still benefits as the infrastructure substrate, but more of the margin shifts up to the assistant layer.