In this episode, we sit down with Hannes Mühleisen, co-founder and CEO of Duck Labs and co-creator of DuckDB, for a wide-ranging conversation about how a self-described outsider ended up reshaping the analytics database world.
Hannes shares how he accidentally fell into databases after moving to Amsterdam, why that outsider perspective helped him spot the “warts” everyone else had accepted, and his theory that traditional databases were “sold on the golf course” rather than built for the people who actually use them.
We dig into the origins of DuckDB: the decision to throw away a working prototype and rebuild from scratch, the untapped gap between Excel/pandas and Spark, and why in-process analytics unlocked a whole new class of users. Hannes also explains the “venture communism” reasoning behind open-sourcing a project built with Dutch tax dollars, how a single Hacker News post lit the fuse, and the philosophy of solving one real user problem at a time.
Finally, we get into the latest work — DuckLake, the Quack client-server protocol, the “never give up, never surrender” approach to queries that refuse to crash, and what changes when the entity querying your database shifts from humans to machines.
Chapters00:00 Introduction to Hannes and His Journey into Databases
02:35 The Outsider Perspective in Database Development
05:12 The Evolution of Database Sales and User Experience
08:01 The Rise of Open Source in Database Systems
10:56 Building DuckDB: Challenges and Innovations
13:31 The Gap in OLAP Systems and the Emergence of DuckDB
16:05 Creating a New Market for Analytics with DuckDB
19:05 The Impact of Open Source and Academic Roots
21:57 The Philosophy Behind Open Sourcing DuckDB
28:02 The Value of Public Funding in Research
29:46 Open Source Strategy and Market Credibility
31:39 Launching DuckDB: Initial Reactions and Strategies
35:07 Learning from User Feedback and Market Needs
38:38 The Challenges of Database Development
42:34 Innovations in Client-Server Protocols
47:02 The Evolution of Client-Server Protocols
52:57 Future Aspirations for DuckDB and Community Engagement
