WhoBuilt

How Supabase Became One Of The Fastest Growing DevTool Companies In The World

Jul 23, 2026· 31 min· 8.3K views·Watch on YouTube

Speaker

Paul Copplestone, co-founder and CEO of Supabase, discusses how the company grew its open-source Postgres developer platform with a Y Combinator host.

Choosing Postgres and open source

After using Firebase and Postgres, Copplestone built an open-source tool that gained traction on Hacker News. He chose Postgres for its reputation, growing developer interest, and community ownership, which he believed would help it keep improving. Calling Supabase an “open source Firebase alternative” made the product easier to understand and helped it take off.

Building trust and a fast developer experience

Supabase took about a year and a half to earn its first dollar, with early customers often being high-growth startups. Copplestone said the team aimed to reduce the time to launch a database and insert a row from about eight and a half minutes to under a minute. They tracked what developers wanted by listening across communities such as Reddit, Twitter, and Hacker News.

Adapting to AI-built applications

In December 2024, Supabase saw a surge in database launches from companies including Bolt and Lovable. The team debated whether those applications would grow, then developed Supabase for Platforms so companies could launch and manage many databases. Copplestone said agents now launch most databases, and the product direction is moving toward CLIs, MCPs, declarative schemas, and branchable environments.

Staying grounded while scaling

Copplestone said funding should serve the company’s work rather than redirect it, and that cash alone cannot ensure success. Supabase has 360 employees across more than 60 countries, with no offices and decisions documented online. He said that written history now helps agents retrieve old decisions and company principles.

Making databases self-driving

Copplestone’s longer-term bet is self-driving databases that can handle operations such as security, patching, and recovery without waking someone up at night. He sees operating an application after it is built as a harder problem than generating the initial application.

Takeaways

  • Make a product’s value clear in terms developers already understand.
  • Measure how quickly users reach a useful result, then work to reduce friction.
  • Listen to users across the places where they already gather.
  • Treat funding as a resource for the work, not a reason to change direction.
  • Document decisions so people and tools can find and apply them later.

Mentioned in this talk

Search inside this talk

What was claimed 19

Show all 19 facts

Related talks