Latest / The Open Source Business with Fexingo: Commercial Strategy for Free Software Companies / The Developer Tax That Killed Open Source Projects
Transcript
- Lucas: There is a specific kind of silence that falls over a Slack channel when an open source company announces a license change. It is not the silence of anger, exactly. It is the silence of people realizing the social contract has just been rewritten without their consent. Luna: And usually, by the time the silence breaks, the fork has already been created. I remember watching the GitHub stars drop on several projects after those announcements last year. Lucas: Right. And we have covered a lot of ground on this show about how these companies make money. Dual licensing, cloud partnerships, managed services. But today I want to talk about the thing that almost never makes it into the pitch deck: the developer tax. Specifically, the moment when the people who built the community start feeling like they are being taxed for using the very tool they helped create. Luna: Because until recently, the implicit deal was that if you used it commercially, you could either contribute back or buy a commercial license. That balance felt fair. Lucas: It felt fair because the alternatives were terrible. Before the modern era, if you wanted to use a database or a networking tool in production, you were often left to fix bugs yourself. The commercial open source model offered a safety net. You got stability, security patches, and a vendor to call when things broke. In exchange, the company got revenue and control over the core intellectual property. It was a symbiotic relationship. Luna: But symbiosis requires mutual benefit. When one side starts extracting more value than it provides, the other side leaves. That is biology, and it is also business. Lucas: Exactly. And the pivot point for me was looking at HashiCorp's move in early two thousand twenty four. They shifted their primary products to the Business Source License. For those listening who might not know the specifics, BSL allows free use for a set period, but then restricts commercial competition. It is designed to stop hyperscalers from taking the code, wrapping it in a proprietary cloud service, and selling it without sharing the profits. Luna: Which sounds reasonable for the founders. Why should Amazon take your work and sell it as a managed service while you struggle to pay your engineers? Lucas: It is reasonable from a capital markets perspective. Investors want protection. They do not want to see a successful project get acquired by AWS for zero dollars because AWS can just re-implement the core logic. But from a developer perspective, the reaction was visceral. Developers did not care about the capital structure of HashiCorp. They cared that the tool they relied on for daily operations had suddenly become politically charged. Luna: I saw that thread on Twitter where a senior DevOps engineer said he stopped contributing to Terraform modules immediately. He said it felt like signing a non-compete clause just for reading documentation. Lucas: That is the key phrase. It felt like a non-compete. Because once you change the license, you are effectively saying that anyone who builds on top of you, anyone who creates a derivative work, is now a potential competitor rather than a partner. You have moved from a community model to a walled garden model overnight. Luna: And the irony is that the people most likely to be blocked by these restrictive licenses are often the ones who provide the best feedback and bug fixes. Lucas: Precisely. So let us look at the data from the second quarter of two thousand twenty six. We are seeing a divergence in the market. On one side, you have legacy open source giants trying to tighten their grip. On the other side, you have a new wave of projects that are refusing to play that game. They are adopting different strategies to capture value without alienating the core user base. Luna: Like what? Are we seeing more companies go fully open core, or is there a third option emerging? Lucas: We are seeing a return to what some analysts are calling the 'Trust-First' architecture. The idea is that you monetize the friction, not the code. Let me give you a concrete example. There is a company called Grafana Labs. They have a massive community around their observability platform. They did not try to lock down the core engine with a restrictive license. Instead, they monetized the complexity of managing that engine at scale. Luna: So they offer the tool for free, but charge for the hosting, the alerts, and the integration with enterprise identity systems? Lucas: Yes. And they backed it up with a commitment to keep the core under an Apache two license. That matters. It signals to developers that their contributions will remain free forever. You do not have to worry that next month, your favorite plugin will become proprietary. That certainty is worth millions in reduced churn. Luna: But doesn't that leave them vulnerable to someone just forking the code and offering the same thing cheaper? Lucas: It does. But here is the thing about open source that investors often forget. The code is rarely the moat. The moat is the network effect. If everyone is using Grafana, the plugins are built for Grafana. The integrations are documented for Grafana. The consultants are certified in Grafana. If you fork the code, you still have to rebuild the ecosystem from scratch. That is a much higher barrier to entry than just copying a license. Luna: So the license is just a legal shield, but the community is the actual economic engine. If you damage the community, you damage the engine. Lucas: I think that is the central thesis of this episode. We are entering a period where reputation is the primary currency. In September twenty twenty six, if you are a CTO evaluating a software vendor, you are not just looking at their price to earnings ratio. You are looking at their commit history, their response times on GitHub issues, and the tone of their community forums. Luna: Because if the developers hate you, they will sabotage your product from the inside. Or they will migrate to a competitor that treats them better. Lucas: Or they will simply stop using it. And in the world of developer tools, abandonment is quiet. No one sends a cancellation email. They just switch to a different dashboard and update their resume. Luna: It reminds me of the old Red Hat days. They won because they made the open source experience reliable. They didn't try to hide the source code. They sold the guarantee. Lucas: Red Hat understood that enterprises are risk-averse. They were willing to pay for insurance. But today, the risk profile has changed. Enterprises are worried about supply chain attacks, license compliance, and vendor lock-in. They want partners who are transparent, not secretive. Luna: So what does a transparent commercial strategy look like in practice? Is it just about being nice to developers? Lucas: No, it is about aligning incentives. Look at how some newer companies handle their governance. They establish independent foundations early on. They let the community vote on technical direction. They publish their financials more openly than traditional SaaS companies. It creates a sense of shared ownership. Luna: Shared ownership changes the dynamic completely. You are no longer fighting against the users. You are working with them. Lucas: And that leads me to the donation segment, because this conversation is getting a bit heavy on theory. If these conversations are useful for what you're building or running, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, it really helps keep the research sharp. Thanks for considering it. Lucas: Let us get back to the practical side. We talked about Grafana. What about the other end of the spectrum? The companies that failed to navigate this transition. Luna: Well, MongoDB comes to mind. Their shift to the Server Side Public License was a massive red flag. It was so restrictive that even friendly forks couldn't operate legally. Lucas: Right. And the result was predictable. The community splintered. You got Mongosh, which was a direct fork of their shell, created by contributors who refused to accept the new terms. You got a fragmentation of the ecosystem that hurt everyone. Users had to decide which version to adopt. Developers had to choose sides. The company lost momentum. Luna: It is a cautionary tale. You can try to squeeze more revenue out of every dollar, but if you kill the growth engine, you have nothing left to squeeze. Lucas: Exactly. And this brings us to the current state of the market in late two thousand twenty five and into twenty twenty six. We are seeing a consolidation of the 'good' open source companies. Those that maintained trust are growing faster than those that tried to restrict access. The valuation multiples are reflecting that. Investors are paying a premium for sustainable, community-backed platforms. Luna: So the advice for founders is basically: don't be greedy with the license. Protect your IP, yes, but don't weaponize it against your users. Lucas: Protect your IP, absolutely. But do it through pricing tiers and feature segmentation, not through legal threats. Sell the convenience, not the code. Sell the support, not the source. Keep the core open, and let the ecosystem grow around you. Luna: It feels counterintuitive in a world where everyone is obsessed with defensibility. But maybe defensibility comes from loyalty, not locks. Lucas: I think that is the shift we are witnessing. The era of the closed fortress is ending. The era of the open platform is returning, but this time, it is commercial. It is profitable. And it is built on trust. Luna: If you are building a developer tool right now, ask yourself this question: would my users fork me if I changed the license tomorrow? If the answer is yes, you have a problem. Lucas: That is a good metric. And it is one that many founders ignore until it is too late. They think they are building a business, but they are actually building a commons. And you cannot privatize a commons without destroying it. Luna: So where do we go from here? Are we going to see more foundations? More independent governance structures? Lucas: I think we will. Especially as AI generates more code, the distinction between human-written and machine-generated open source will blur. Trust in the provenance of that code will become even more valuable. Companies that can prove their lineage, that can show their contributors, that can demonstrate their ethical standards, will win. Luna: Provenance as a feature. That is a compelling idea. It turns transparency into a competitive advantage. Lucas: It does. And for listeners who are operators, the takeaway is simple. Treat your community like your shareholders. Listen to them. Respect their labor. And never, ever surprise them with a change that devalues their contribution. Luna: Because in the end, the code is just text. The value is in the people who read it, write it, and rely on it. Lucas: Agreed. So as we wrap up, I am curious. Have you seen any recent examples of companies getting this right? Or any moves that surprised you with their backlash? Luna: I noticed that PostgreSQL Foundation's steady, boring governance model is attracting more enterprise investment than ever. Maybe boring is the new sexy. Lucas: Boring is reliable. And in business, reliability is the ultimate luxury. Thanks for tuning in.