At a glance
WHAT IT’S REALLY ABOUT
Supabase’s agent-driven growth proves cash doesn’t equal real success
- Paul Copplestone explains why Supabase bet on Postgres: an increasingly popular, community-owned database whose ecosystem flywheel makes it a durable long-term foundation.
- Supabase committed to truly permissive open source (MIT/Apache/Postgres) and monetizes by running the hard operational parts of Postgres rather than withholding features behind an open-core model.
- The company’s breakout came from crisp positioning as an “open source Firebase alternative,” then winning developers on predictable pricing, relational data, and open-source credibility.
- Supabase’s growth accelerated across three AI waves—pgvector/RAG, vibe-coding platforms launching massive numbers of small databases, and agentic coding (Claude Code) driving faster activation and conversion.
- Agent-driven usage is reshaping Supabase’s DX priorities toward CLI/MCP-first tooling, code-defined workflows, and tighter dashboard-to-git synchronization while the company scales from ~220 to ~360 people.
IDEAS WORTH REMEMBERING
5 ideasPostgres was the “old tech” bet precisely because it’s community-owned and compounding.
Copplestone framed Postgres’ durability as an ownership advantage: because no single company controls it, contributions and adoption compound over time. That ecosystem “flywheel” makes Postgres a stable foundation for building a long-lived database business.
Supabase monetizes operational complexity, not proprietary features.
Supabase chose permissive licenses (MIT/Apache/Postgres) and avoided open-core gating, betting that the managed-service difficulty (backups, failover, ops) is the natural monetization. Their differentiation is building an ecosystem around Postgres and contributing upstream rather than inventing a proprietary “Postgres-like” database.
A clear category frame (“open source Firebase”) unlocked distribution more than raw features did.
Early traction was limited under the “real-time Postgres” positioning; changing the tagline to “open source Firebase alternative” made the value prop instantly legible and triggered a top-of-Hacker-News breakout. Even without feature parity, the aspirational comparison clarified who the product was for and why it mattered.
Supabase’s wedge against Firebase was trust + relational data + predictable economics.
They won developers by addressing common Firebase pain points: pricing/bill shock, NoSQL limitations, and Google lock-in sentiment—while offering relational Postgres, predictable pricing, and true open source. Over time this credibility shift is reflected in adoption (e.g., a claimed 60%+ of a recent YC batch using Supabase).
AI didn’t just add new users—it changed the quality and lifecycle speed of Supabase workloads.
Copplestone described three AI-driven growth waves: (1) pgvector/RAG adoption, catalyzed by an outside contributor who added pgvector and helped build an early “chat with docs” demo; (2) the vibe-coding platform wave (Lovable/Bolt) creating massive database-creation bursts; (3) Claude Code/agentic coding driving higher-intent builds where activation, conversion, and revenue curves all rose together.
WORDS WORTH SAVING
5 quotesbig problems, big, hairy problems present good opportunities for a startup founder.
— Paul Copplestone
Postgres belongs to no one.
— Paul Copplestone
on one day, we changed the tagline from real-time Postgres to open source Firebase alternative.
— Paul Copplestone
over 60%, uh, of databases are launched by an agent.
— Paul Copplestone
staying grounded is largely a factor of just remembering that the cash actually doesn't mean that you're successful.
— Paul Copplestone
High quality AI-generated summary created from speaker-labeled transcript.
