All episodes

PMF is one pivot away with Ant Wilson from Supabase

Supabase cofounder Ant Wilson explains how a positioning change unlocked product-market fit, why developer memes can reach the enterprise, and how a 30-year database ambition translates into three-month plans.

Jack Bridger
Episode 4237:19

Supabase began as a real-time Postgres project and broke through when the founders described it as “the open-source Firebase alternative.” The underlying work had not suddenly changed; the message gave developers a frame they already understood.

Ant Wilson joins Jack to unpack that pivot, Supabase’s feedback and marketing systems, the combination of developer experience and Postgres-scale credibility, and the long-term ambition behind the company.

The Q&A below is experimental — extracted from the episode transcript with AI. If you spot a mistake, let us know at jack@scalingdevtools.com.

What is Supabase?

Supabase is an open-source Firebase alternative built around Postgres. It combines a hosted or self-hosted database with authentication, real-time updates, storage and related backend services. Ant is a cofounder and was serving as CTO, bringing experience from two previous startups and from large-scale storage systems.

What made starting a company feel possible?

As a child, Ant could imagine being an Egyptologist but could not see a route into that career. Years later, The Launch Pad—a book about Y Combinator—made startups similarly concrete: a small group of friends could build on the internet, apply to YC and turn that into a company. That visible path was enough for him to leave his job and try.

Was Supabase’s product-market fit really one pivot away?

Yes, but the decisive pivot was positioning rather than a wholesale rebuild. The original “real-time Postgres” pitch attracted roughly one new hosted database a week. Calling the same product an open-source Firebase alternative gave it a familiar category and produced a surge from eight hosted databases to roughly 800 in three days after a Hacker News launch. That demand supplied the confidence and momentum to expand into auth, storage and the broader platform.

How does Supabase prioritize a firehose of feedback?

Feedback arrives through GitHub issues and discussions, the website, email and social media, then funnels into a tagged Notion system owned by the relevant product teams. The important distinction is repetition: a request heard from many users has more weight than the most recent or loudest message. Centralizing the evidence helps the team avoid recency bias without losing the qualitative context.

How can one product serve beginners and enterprises?

Supabase aims for a Vercel-like developer experience while making it clear that the system can scale and will not create a surprise bill. Postgres supplies a trusted foundation rather than asking users to believe an unknown startup database, and the team contributes upstream to Postgres itself. The two rails are simple onboarding and credible scalability: easy enough for a weekend project, dependable enough to grow with it.

Why do Supabase’s memes work?

They create broad brand awareness across developer culture, which fits a database usable from many languages and stacks. The resulting search demand is heavily branded: developers look specifically for Supabase and the feature they need. More importantly, enterprise developers are the same people who build side projects and read developer jokes; a bottom-up sale does not require pretending that everyone inside a large company communicates like a boardroom.

How did the team find its marketing mix?

Through deliberate trial and error. The founders were not active Twitter users before Supabase, so they tested formats there, then tried Reddit, meetups, Instagram, TikTok and other channels. Each channel taught them something about efficiency and audience. The lesson is to test broadly enough to discover the combination that works instead of importing another company’s playbook as a certainty.

At what moment does Supabase want to be remembered?

The insertion point is the start of a new project. Databases are sticky, so winning a greenfield workload is much easier than persuading someone to migrate an existing one. Supabase uses spaced repetition across social, communities, podcasts and launches so the same clear message is available at that moment. Postgres portability also reduces the perceived risk: a user can take a standard dump and restore it elsewhere rather than accept a proprietary dead end.

What does the 30-year version of Supabase look like?

The team imagines an ultimate database that blends transactional and analytical workloads and lets users manipulate more data without assembling many external systems. It plans toward that destination while reassessing the next few months every quarter. Ant sees two durable waves underneath the work: Postgres becoming the default choice for more developers, and large companies replacing expensive Oracle estates with open technology—creating room for an “open-source Oracle.”

What is Ant’s biggest lesson for DevTools founders?

Iterate on the message as seriously as the product. A good product is easier to market, but founders must still experiment with the language, audience and place where they pitch it. Supabase’s own breakthrough came from explaining existing work in the category developers needed; treating positioning as fixed would have hidden the product-market fit already within reach.

Keep listening