What this covers
Patrick hosts Chetan, an investor whose portfolio has produced four open source exits (MongoDB, MuleSoft, Elastic, Acquia), and Jeremiah, who speaks from building Prefect, a workflow engine company. Chetan brings the investor's view and the figures. Jeremiah brings the operator's view, including what Prefect's paying customers actually value. The conversation asks what a company is selling when the code is free, and why most open source projects never become businesses.
The middle of the discussion is about the clouds. Chetan describes how AWS, Azure, and Google Cloud forced open source companies to rethink licensing and go-to-market, and he cites MongoDB's Atlas, which went from a June 2016 launch to a $210 million run rate. Jeremiah argues that clouds ultimately sell compute and storage, so an open core company that only manages its own software ends up competing with them. He also names the perverse incentive to make the free product hard to use, and he raises survivorship bias in how outliers get discussed. Chetan adds that open source has won mostly in infrastructure, not end-user applications.
The last stretch turns to community. Jeremiah's health test is how often an unpaid outsider answers a community member's question. Patrick contrasts a magnet with a megaphone and argues that companies err by hoarding what feels proprietary but costs little to distribute. He also stresses that unwelcoming maintainers drive people away.
Open source businesses sell the expertise, convenience, and reliability built around free code rather than the code itself, and they succeed only when the core is dramatically better than alternatives and aligned with cloud trends, while community trust is both the moat and the main exposure.
- Customers pay to avoid pain or effort (insurance-style reliability, managed convenience), not for source code
- Public clouds sell compute and storage, so open core products that merely manage open source software compete with the clouds
- Open source makes community engagement and absence of engagement publicly visible, which is both a trust asset and a risk
Open source becomes a good business only with dramatically better core value and defensibility.
- A cloud-delivered open source service becomes a great business if it provides a dramatic improvement over available alternatives, and that service itself carries defensibility beyond the open code.
“If you can provide a service or an offering to customers that is a dramatic improvement to the alternatives that are available, it will lead to becoming a great business”
- Chetan's portfolio has produced four venture 'exits' from open source companies (MongoDB, MuleSoft, Elastic, and Acquia), and he points out that the vast majority of open source projects do not become good businesses even though a few do.
“the number of open source companies that have become very successful businesses as a percentage of total open source projects is very, very small.”
- Without a core open source project delivering value dramatically better than what is available, it is very hard to justify building an open source business, because the difficulty is high and the success base rate is low.
“without that distinction, it's really hard to make the case of putting yourself through building an open source business”
- Open source is worth pursuing despite its difficulty because the explosion of open tooling has radically increased developer productivity and built a large economic opportunity when it works, with the best outcomes delivering value to users of both open projects and cloud or enterprise products.
“when it works and when you do get it right, it works in an extraordinary way and delivers value to not only the open source users, but also the users of the cloud service”
- Based on 25 years of data, the vast majority of open source projects end up as great projects but not good businesses, so a business case requires significant core value that can later support proprietary modules.
“All the data over the last 25 years indicates that the vast majority of open source projects don't end up being good businesses, they just end up being great projects.”
Infrastructure is where open source businesses win, driven by enterprise spending and cloud-enabled reinvention.
- Chetan estimates the enterprise market spends about a trillion dollars a year and that parts of its infrastructure and application stacks are now being reinvented, with open source driving part of that movement.
“basically a trillion dollars a year that's spent on the entire enterprise market now sort of unlocking itself”
- Open source businesses have been most successful in infrastructure, where open source components are differentiated from existing solutions, whereas end-user applications rarely become big open source businesses because most value comes from end-to-end experiences.
“Where open source businesses have been successful is infrastructure and the sort of idea there is, is that the open source infrastructure that you put out there is actually differentiated than existing solutions.”
- A new trend called super infrastructure consists of API-enabled components that let companies outsource a core function to one API call, and it is particularly attractive to open source companies, citing Shopify, Stripe, Contentful, and Commerce Layer.
“we're starting to see this new trend of what I like to call "super infrastructure" which is essentially API enabled infrastructure that enables you to outsource a core function to an API call.”
- Cloud migration and an explosion of enterprise data across applications, servers, and infrastructure create opportunities for new storage, database, analytics, and processing tools, and enable machine learning, and enterprise workflows that are still largely manual are ripe for open source disruption.
“what's also happened behind that is that data has exploded within sort of enterprises.”
Red Hat, MongoDB, Elastic and other open source exits show the model can work commercially.
- Red Hat formed in 1993 from two companies, a catalog business selling Linux and Unix accessories and Mark Ewing's Red Hat Linux distribution, merged in 1995, and went public in 1999 with one of the largest first-day gains in Wall Street history.
“Red Hat became public in 1999 and, lost in history, but Red Hat had I think like the eighth biggest or the 10th biggest first day gain in the history of Wall Street.”
- Red Hat's public listing and dramatic debut put open source into the spotlight, and its being framed as a disruptive force with a well-capitalized corporate backer helped establish open source as a viable commercial business model in software.
“I think that announcement to the world... was a real fire starter for thinking about open source as an incredible commercial business model in software.”
- IBM acquired Red Hat in 2018 for about $34 billion, after Red Hat had transformed substantially over 25 years from its public debut.
“ultimately of course IBM acquired it for 34 billion in 2018.”
- Benchmark's first fund invested in Red Hat, and the same fund also invested in MySQL, another pioneer of the open source business model that Sun later acquired.
“the group had also invested in MySQL which had also been pioneering the open source business which of course then Sun bought.”
- Salesforce acquired MuleSoft in early 2018 for about $6.5 billion, one of the open source exits in Chetan's portfolio.
“Salesforce ended up buying MuleSoft in early 2018 for about $6.5 billion dollars”
- MongoDB's Atlas went from launch in June 2016 to a $147 million annual revenue run rate within three years and reached a $210 million run rate by Q1 of the following year, with 16,800 customers at end of Q1.
“Atlas in terms of revenue run rate has grown from zero to $147 million of annual run rate revenue within three years after launching.”
- MongoDB's Atlas managed cloud service, which handles replication, security, auditing, scaling, and provisioning across AWS, Azure, and Google Cloud, is now MongoDB's fastest-growing segment.
“If you look at MongoDB's business today, Atlas is by far the fastest growing segment of the company.”
Public cloud forced open source companies to rethink licensing, monetization, and go-to-market strategies.
- The rise of public cloud, dominated by AWS, Azure, and Google Cloud, forced open source companies to rethink both their licensing and their go-to-market strategies.
“Open source companies have had to evolve in how they think about not only licensing, but also how they think about going to market.”
- In the late 2000s it was viable to make software completely open and monetize through enterprise tooling and services that customers ran in their own data centers, with the commercial entity helping startups stand up the project, a route Chetan believes is largely unavailable today.
“In the late 2000s, it was a totally viable business model to say that I'm going to have a completely open software and the way that I'm going to monetize is offer services and "enterprise" tooling”
- Google, Microsoft, and AWS have adopted sharply different approaches to running and monetizing open source projects as cloud services, and this landscape is still in very early evolution.
“the three public clouds have taken dramatically different positions and postures about how they think about running their own services on top of open source projects.”
- Microsoft, which once famously called Linux a cancer, is now one of the largest contributors to the open source world, illustrating how companies have come to embrace open learning.
“There's perhaps no better example of this than Microsoft which famously called Linux a cancer many years ago, but is now one of the biggest contributors in the open source world.”
Independent developers and enterprises now benefit from open tooling and greater openness to new workflows.
- The explosion of open source tools and public clouds in the late 2000s and 2010s means independent developers can now build high-quality applications faster than large consumer internet companies that once had proprietary internal tooling advantages.
“building an application today of extraordinarily high quality, you can do it actually much faster than some of the large consumer internet companies primarily because of the number of open source tools that are available and the advent of public clouds”
- Enterprises, large and small, have shifted to asking why workflows have been done a certain way for 20 years and are more open to new tooling that does things better, faster, and cheaper.
“enterprises, large and small are now of the mindset of well, if it's been done that way for 20 years, why has it been done that way?”
- In the early and mid-2000s, independent developers were disadvantaged because little open source tooling existed to help them build quickly, while large consumer internet companies had proprietary internal tooling that gave them distinct speed advantages.
“building an application today of extraordinarily high quality, you can do it actually much faster than some of the large consumer internet companies primarily because of the number of open source tools that are available and the advent of public clouds”
Community contributions and public engagement attract talent, extend reach, and guide product roadmaps.
- Elastic disclosed in its S-1 filing that its products had been downloaded about 350 million times and that it had roughly 200 meetup groups across 46 countries, showing the scale of a global developer community that carries responsibility.
“We disclosed that our products have been downloaded on the order of 350 million times.”
- Publishing a company's unsolved problems and lessons attracts talented engineers, since people want to work on interesting problems, which creates a second-order talent benefit beyond product improvement.
“it also has a second derivative effect of being an enabler of attracting really great talent to the company because you are now essentially showcasing really interesting problems”
- The vast majority of open source community members contribute knowledge through talks, content, and feedback rather than code, and that community feedback guides the company's roadmap toward what users need.
“The vast majority of people that are in the open source community will not contribute a ton of code back into the open source project, but they will contribute a lot of knowledge.”