How Supabase Became One of the Fastest-Growing DevTool Companies in the World

Chapter 1 · Narration: WOW Mentor

How Supabase Became One of the Fastest-Growing DevTool Companies in the World

What WOW Mentor dissects here is that Supabase did not simply get lucky riding the AI boom — it had spent years assembling the strategic choices that let it absorb that boom whole. On his third startup, Paul Copplestone stacked an open-source philosophy on top of Postgres, a technology nobody owns, drove time to value toward zero, and treated the community as the product's compass. So when the explosion arrived — Bolt, Lovable, and then Claude Code — Supabase already had the vessel ready to catch it. The last thing WOW Mentor highlights is that he has already moved his sights to the next battleground: not the build stage, but the operate stage.

Today, WOW Mentor breaks down one of the fastest-growing developer-tool companies the world has seen: Supabase. Founded in 2020 as an open-source tool to help people host Postgres online, it became a decacorn — valued over ten billion dollars — just a few years later. Co-founder and CEO Paul Copplestone tells it with striking calm, more interested in how the numbers came to exist than in flexing them. Even now, with the company exploding, he says what keeps him grounded is an absolute certainty that money will not solve his problems — and that, he insists, is good news for early-stage startups too. What WOW Mentor highlights first is not the spectacular outcome but the repetitive, unglamorous choices beneath it. Growth is not an event; it is an accumulation. He explains that Supabase is his third venture-backed startup. Raised in New Zealand by an entrepreneur father, he says the instinct is in his blood; he did one corporate consultancy job, hated it, and has done nothing but startups since. His first, where he was CTO, never found product-market fit, and he left over a clash with his CEO on direction. The second was different: a co-founder he had worked with before said 'give me two years, be my CTO, help me launch this,' and while building that business he was quietly incubating Supabase in the back of his mind. When the moment felt right, he walked out and launched; that second company is still alive and even profitable. What WOW Mentor highlights is that even the failed or handed-off ventures were raw material: he knew he wanted a dev-tools and database company, but not exactly how — certainty of direction, humility about method. When the interviewer suggests startups fail mostly from running out of money, he immediately overturns the cliché. He explains that the data shows companies die because founders give up, because of drama, or because they never find product-market fit — and that people usually close their companies while they still have plenty of money in the bank. What WOW Mentor underlines is that misdiagnosing failure leads to the wrong prescription: if you believe money is the problem, you chase more funding; but if the real problem is fit, endurance, and alignment between founders, capital only delays the death rather than preventing it. At the heart of Supabase sits Postgres, roughly forty years old in its earlier forms. He explains that at his previous company he used both Postgres and Firebase, hit scaling limits on Firebase, migrated to Postgres, wrote an open-source tool in the process, and put it on Hacker News. It got traction, and only three or four months later he launched Supabase properly. Reading Hacker News three times a day, he could see Postgres rising before it was the most popular database. What WOW Mentor highlights is his game theory: he asks which database will win over the next fifty years and wagers on Postgres, because nobody owns it, so everybody contributes to it; every hyperscaler is then forced to offer the best possible Postgres, and it keeps improving in a flywheel. And because databases are incredibly hard to build, the reputation Postgres already carried mattered too. Ride a technology nobody owns, and the ecosystem grows it on your behalf.

But the right technology does not land on its own. He recounts building a real-time engine on top of Postgres first, convinced that was the thing — and it did not really take off. The moment he changed the tagline to 'open-source Firebase alternative,' growth exploded. What WOW Mentor highlights is that the product had not changed, only the sentence describing it. People already loved Firebase — a legitimately good tool — but craved the two things it lacked: Postgres and open source. The positioning simply named a desire the market already carried; the only barrier left was trust. It was not the first thing he built that was the answer, but the first framing that landed. The open-source strategy he chose was a philosophy and a moat at once. For him open source was a belief he and his co-founder shared, not a tactic — yet the defensive line it created is intensely practical. Supabase gives essentially everything away; there is no paid enterprise version held back. The one thing not available is how to host a million databases — and even that is not concealment but a matter of the code being ridiculous spaghetti, lumped in with billing logic, such that releasing it would be a security nightmare. On the risk of a cloud provider cloning and reselling it, he notes the familiar pattern where hyperscalers take Redis or Elasticsearch and out-earn the creators — but Supabase stands in the opposite position: the providers already host Postgres through RDS and Aurora, so what would they even take? And Supabase is a stack of tools working together, far harder to manage than a single Redis instance. What WOW Mentor highlights is that the real moat is not hiding code but handling that complexity gracefully. His account of monetization and early customers is a narrative of patience. They thought about monetization from the get-go, but it took about a year and a half to earn their first dollar. Databases are extraordinarily hard to break into, but once you do, they grow naturally — you go to sleep and the business keeps growing, with a database underneath. So the ideal early customer was a venture-backed company likely to grow fast — a Y Combinator startup — which is why they applied to YC. Today over 60% of every batch uses Supabase, and they use Supabase to build Supabase. Yet in their own batch, no one trusted them — maybe one company — and because it was remote, they had to go straight out to the internet. Revenue exited the first year around a million in ARR, then seven and a half the next. Slow going by today's standards — and he warns the press only reports the crazy outliers who supposedly go to a hundred million in a month. The core metric of Supabase's early strategy was time to value. He recalls timing how long it took to launch an RDS instance on AWS, connect, and insert a single row: about eight and a half minutes. He decided they had to get that under a minute, and tracked it obsessively. Today it is around five seconds, while RDS is probably still eight and a half. Tellingly, he never shouted this speed from the rooftops; it simply becomes an innate part of the developer's experience — and he does not push the community to follow him but relentlessly asks developers what they want and listens, wherever they are. What WOW Mentor highlights is that he redefines this metric for the agent era: what matters now is not merely being fast but reaching the result with as little input as possible — a one-shot, where an agent that needs re-prompting is a loss of value.

… The rest of this chapter continues in the full edition, available with a subscription.

Listen to this chapter