Jun 25, 2026 · 1h 2m · in-depth
The egoless culture that built Supabase | Paul Copplestone (Co-founder, CEO)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this in-depth interview, Supabase co-founder and CEO Paul Copplestone shares the technical foundations, product-led growth strategies, and egoless leadership philosophy that turned an open-source project into a generational database platform. He discusses navigating hypergrowth driven by AI app builders, maintaining open-source integrity without vendor lock-in, and scaling a high-performing asynchronous organization.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Brett holds 17.4% of the talking time here. How this is scored →
Brett as informed peer 4.0 Guest teaching 5.5 Guest disagreement 1.3 Brett pushing back 1.2
speaking balance: gold is Brett, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 42:35 Pushing back against investor pressure on company culture
Paul forcefully rejects the conventional investor premise that an undeniable, high-performing culture cannot coexist with an egoless, kind environment, explicitly noting he told investors they were wrong.
Hardest push from Brett ▶ 2:50 Challenging the founder's initial ambition levelBrett presses Paul on whether his mindset during his first startup was inherently less ambitious than when building Supabase, prompting Paul to clarify the distinction between ambition and market constraints.
Biggest teaching moment ▶ 49:40 Deconstructing traditional sales compensation in PLGPaul educates Brett on how Supabase turned traditional software sales on its head by treating sales as technical support and measuring revenue growth against an uncontacted control group.
Brett holds their own ▶ 50:58 Interrogating the mechanics of technical sales engineeringBrett drills into the specific composition and quota structure of the sales team, demonstrating his sharp understanding of enterprise sales structures and incentives.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Brett as informed peer | Guest teaching | Guest disagreement | Brett pushing back | Why |
|---|---|---|---|---|---|---|
| Early Startup Experiences and Technical Foundations | 4 | 4 | 2 | 2 | Brett probes Paul's earlier, less successful startups, clarifying whether Paul had a less ambitious mindset or merely faced structural market constraints. Paul politely rejects the premise that his initial mindset lacked ambition, pointing instead to geographic limitations and missing product-market fit. | |
| Y Combinator Acceptance and Postgres Tailwinds | 4 | 5 | 1 | 1 | Paul explains the origin of Supabase out of real-time chat limits on Firebase and his realization that Elixir/Phoenix on Postgres could solve it. Brett asks about Paul's psychological conviction level, prompting Paul to articulate how developer database friction created an undeniable opportunity. | |
| Founder Evolution, Mindset Shifts, and Async Culture | 4 | 6 | 2 | 1 | Paul reflects on unlearning the New Zealand 'tall poppy' syndrome, separating fundraising mechanics from building, and embracing fully asynchronous distributed teams. Brett listens as Paul details how avoiding premature blitzscaling became an ingrained lesson. | |
| Reverse Engineering Supabase's Moat and PLG Motion | 4 | 6 | 1 | 1 | Brett asks Paul to reverse engineer Supabase's moat in hindsight. Paul breaks down the distinction between the 'build' space and 'operate' space, explaining how operational reliability over years forms the true moat rather than just shipping features. | |
| Positioning Fit, Launch Weeks, and Primitives Strategy | 4 | 6 | 1 | 1 | Paul describes how changing their tagline to 'Open Source Firebase Alternative' sparked viral Hacker News traction, leading to the invention of Launch Weeks and a primitives-first product philosophy. Brett asks whether technical taste or customer requests drove the roadmap. | |
| Managing Product-Market Fit and Lean Teams | 4 | 5 | 2 | 2 | Brett explores the balance between founder skill, timing, and luck. Paul explains why staffing up before finding product-market fit is a mistake, insisting on keeping feedback loops small and operating lean even with substantial funding in the bank. | |
| Evolving Product Pipelines and Developer Experience Philosophy | 4 | 5 | 1 | 1 | Paul contrasts early improvisational shipping with current staged pipelines (Labs, alphas, betas) required for eight million developers. He defines great developer experience concretely around minimizing time to value and eliminating paper cuts. | |
| Solving Graduation Risk and Commitment to Open Source | 4 | 6 | 1 | 1 | Brett asks how Supabase avoided the classic Firebase graduation problem. Paul explains the deliberate strategy of capturing Day 0 workloads under the Firebase alternative banner while smuggling Postgres underneath, backed by an uncompromising commitment to open source. | |
| AI Builders, Hypergrowth, and Infrastructure Challenges | 4 | 6 | 1 | 1 | Paul outlines three waves of AI adoption: PG vector, AI app builders like Bolt/Lovable, and CLI/MCP agent workflows. He discusses internal skepticism over 'vibe coding' slop and the operational crunch of running out of IP addresses during hypergrowth. | |
| Scaling Headcount and Overcoming the Hero Culture | 4 | 5 | 1 | 2 | Brett questions how Paul managed recruiting and organizational phases up to 200 people. Paul explains how a policy of only hiring for 'hair on fire' problems created an unsustainable hero culture that eventually required intentional scaling of headcount. | |
| CLI-First Workflows and Self-Driving Databases | 4 | 6 | 1 | 1 | Paul discusses the three-year horizon shift from dashboard-first to CLI-first and Git-declarative workflows suited for AI agents. He outlines the future of self-driving databases where agents monitor, secure, and optimize database health autonomously. | |
| Distributed Async Culture and Egoless Team Values | 4 | 6 | 2 | 1 | Paul describes Supabase's fully asynchronous culture, embedding company history into searchable AI warehouses, and defining an egoless yet hyper-competitive ethos rooted in traditional open-source values. | |
| Kind Leadership, High Standards, and Authenticity | 4 | 5 | 2 | 1 | Brett observes Paul's genuine kindness compared to the stereotypical cruel CEO archetypes. Paul explains his belief in non-zero-sum games and rejects investor dogma claiming high standards and egoless humility cannot coexist. | |
| Strategic Playbook for Venture Capital Fundraising | 4 | 5 | 1 | 1 | Paul outlines his practical approach to fundraising, contrasting how founders must over-communicate ambition with investors due to implied discounting, while under-promising and over-delivering with developers. | |
| Layered Enterprise Expansion and Product-Led Sales | 5 | 7 | 1 | 2 | Brett digs into how Supabase balances enterprise requirements with PLG. Paul gives a detailed breakdown of their product-led sales motion: detecting database stress triggers, providing helpful engineering support, and compensating sales purely on measured incremental usage uplift. | |
| Anti-Lock-In Principles and Navigating Scaling Pains | 4 | 6 | 1 | 1 | Paul discusses their core anti-lock-in product principle built on open protocols like pgdump, admitting it creates harder product constraints. He also candidly describes the pain of founder burnout, giving away Legos, and helping engineers escape hero cultures. | |
| Kaizen Mindset: Process-Oriented Systems Thinking | 4 | 6 | 1 | 1 | Paul explains how applying the Kaizen mindset from the Toyota Production System guides his operational leadership. By focusing on small incremental improvements and unblocking PRD/RFC processes, teams avoid the stalling that large-scope initiatives cause. | |
| Core Motivation, Customer Empathy, and Concluding Remarks | 3 | 4 | 1 | 0 | Brett asks what Paul wants customers and colleagues to say about him when he is not around. Paul emphasizes that he prefers his team feel they built the success themselves rather than crediting him, identifying fundamentally as a fellow builder. |
Statements from this episode (23)
Copplestone: Supabase originated from the tech stack built for Nimbus
“I built Nimbus with the same tech stack and that tech stack now is what is super base.”
Copplestone: Supabase team was engineered specifically to be YC-friendly
“I thought at the time, again, to de-risk things, I thought, I'm going to build a, the most Y Combinator friendly team and apply for YC and that will help from a DevTool point of view. I think that's the pitch that actually convinced him he really wanted to go …”
Copplestone: Startups should never compromise between high agency and high performance
“If you can keep the best people it was at YC yesterday and so on was saying, should I take someone who's high agency or should I take someone who's high performance? And like, it's very clear to me. It's both. Like, you just don't compromise on, on any of thos…”
Copplestone: Remote startups must go fully asynchronous rather than hybrid
“It's very clear to me. No, you don't half-ass it. You just go all in if you're going to do remote. We went completely async, and now, actually, I think it's a superpower for us.”
Copplestone: Operating databases at scale creates a defensible moat against fast launchers
“Where we are is not in the build space. We're in the operate space. We operate the databases. So it's not just enough to launch something. You have to prove that you can operate it over, over many years and do it at scale. So there's this kind of moat that was…”
Copplestone: Supabase resisted pressure to rush upmarket, focusing on community and PLG
“We also leaned very hard into our community and the Pyeongchee motion. So that was good. Not trying to split our focus between Let's go up market really fast. We've just kept our finger on the pulse of the community and the PLG motion, even though we get a lot…”
Copplestone: Product-market fit is often just product positioning fit
“Product market fit often is just like a product positioning fit. Sometimes you can just change some things and that's all that matters. And there are some people in the world that want whatever you're building, even if it's a niche product, you just kind of ne…”
Copplestone: Supabase launches unproven products with zero dedicated engineers
“So we're launching a product at the moment, and there's just no engineers on it. It's just a product person engineering it. And people say, oh, should we staff this up? And I said, well, absolutely not. They don't have an idea baked yet. And so it needs to be …”
Copplestone: Funded founders should still operate with a $100k mindset
“What we did well and what I would do, I think if I was to start again is yes, I'd raise the funds. That's important, but I'd still operate as if I only have a 100,000 in the bank account, you know, where you just got to iterate really fast with a small group o…”
Copplestone: Supabase now serves eight million developers
“We could just kind of push things out and people would adopt them and we didn't have to worry about, you know, eight million developers trying something out on day one now.”
Copplestone: Only Firebase and MongoDB succeeded targeting day zero workloads
“If you look back over the past 20 years, probably the only database companies that have really managed to do well Ah, Firebase and Mongo, and they did well because they targeted these day zero workloads that you kind of would choose them before you even knew w…”
Copplestone: Bolt and Lovable launches initially looked like DDoS attacks
“End of 20, 24 was when the likes of Bolt and Lovable launched, and that was also And interesting, that was kind of the second tailwind. We thought we were getting DDoSed at the time, actually, because we just saw this customer launching lots and lots of databa…”
Copplestone: Supabase developer growth accelerates off a 7-8M user base
“And then phase three is largely from January this year, the likes of Cloud Code and Codex and everything that are just ramping up really, really fast. And these are the tools that are using more of the CLI MCP type workload, and we're seeing huge adoption from…”
Copplestone: Supabase only hired for 'hair on fire' needs until 150 employees
“We had this idea that we'd only hire when we had a hair on fire problem for the first probably four or five years, and so we got to maybe 200 people with that mentality, or a 150 people with that mentality, and then we quickly had to change. Like halfway throu…”
Copplestone: AI agents are shifting developer workflows to CLI-first and Git-first
“Now with agents, they're becoming very CLI first. And so this one's kind of obvious to everyone, but you know, what spills out the other side of this is, okay, what that means is that everything is very code first. It's very Git first.”
Copplestone: AI agents will probably operate self-driving databases in the future
“If agents are building now, then they'll probably be operating in the future. So, at the moment, maybe developers end looking at things, whether the database is healthy or not. But of course, they probably don't want to be doing that, and that's actually where…”
Copplestone: Building in SF is the right approach for 99.9% of startups
“They really want you to come to SAF and be based here and built here, and that is the right approach, I think, for 99.9% of the companies.”
Copplestone: Supabase ingests all communications and meetings into searchable AI warehouses
“Our attrition is extremely low, but the leaning into the async culture has helped because everything's written, everything's recorded, everything's captured in Slack or Notion, or one of our sales meetings is ingested into our warehouses, and this kind of solv…”
Copplestone: Founders must pitch unhedged ambition because VCs discount projections anyway
“In fact, they'll discount anything you say anyway. So if you tell them, ah, you know, we're going to be a billion dollar company, they'll probably think, well, oh, well, they'll only be a five hundred million dollar company. You say ten billion, they'll probab…”
Copplestone: Supabase rejects bespoke enterprise feature requests
“Now, if an enterprise comes in and they say something that is also going to benefit maybe a thousand customers, then we'll add it. But if they say something that's bespoke to them, Then, of course, we'll just end up saying no because we really want to make sur…”
Copplestone: Support outreach boosts Supabase account usage growth to 125% QoQ
“And what we do is we measure those who don't respond, how much did their the usage growth and actually we know like quarter over quarter, it's 25% versus those who have chatted to a success person and that's a 125%. So we can see the incremental uplift from th…”
Copplestone: Supabase compensates sales reps strictly on incremental usage uplift
“Yeah, on the incremental uplift only, which I think is the big difference from what was traditionally done. You know, on a PLG motion, you could easily say, ah, get a salesperson and so on, like, reach out to anyone and then you pay them on, on the revenue gen…”
Copplestone: Only the heroes themselves can fix a startup's hero culture
“And then you get this hero culture internally where they're the only ones that can solve it. But that's very hard to solve because the only people that can solve a hero culture is the heroes themselves. They have to hire those people and train them up and offl…”