Lessons from the NATS Controversy

The recent dispute between the Cloud Native Computing Foundation (CNCF) and Synadia over the NATS messaging system highlights the complex relationship between open source foundations and the companies that support them. There are lessons to be drawn from this mini-saga for both foundations and companies navigating these relationships.

The Foundation-Company Relationship: A Symbiotic Partnership

Open source foundations like the Linux Foundation and its sub-foundations such as the CNCF play a critical role in the open source ecosystem. They provide neutral governance, infrastructure support, and community building for projects that might otherwise struggle with sustainability or face challenges from competing commercial interests.

Companies, meanwhile, contribute code, funding, and developer resources that keep these projects alive and thriving. This symbiotic relationship has fueled the growth of open source software for decades, creating a virtuous cycle where companies benefit from collaborative development while foundations ensure projects remain accessible to all.

However, as the NATS controversy demonstrates, these kinds of relationships aren’t without their problems. When commercial interests and open governance principles collide, the resulting conflicts can threaten the stability of projects and undermine trust in the broader ecosystem.

The NATS Controversy: A Case Study in Governance Challenges

In April 2025, Synadia, the primary contributor to the NATS messaging system, released a proposal to “withdraw” the project from the CNCF and change its license from the open source Apache 2.0 to the more restrictive Business Source License (BSL). This move sent shockwaves through the open source community, as it challenged fundamental assumptions about project governance and the finality of project donations to foundations.

The Timeline of Events

1. 2018: Synadia donates NATS to CNCF, which accepts it as an incubation-level hosted project. Synadia committed to transfer the trademarks to NATS, as required by CNCF policy.
2. 2018-2019: A trademark dispute between Synadia and Major League Baseball over certain marks related to the Washington Nationals baseball team delays the transfer. CNCF reimbursed Synadia for $10,000 of its legal fees from the dispute, but Synadia never actually transferred the NATS trademarks to CNCF.
3. April 2025: Synadia announces its plans to withdraw NATS from CNCF and adopt the BSL license.
4. Late April 2025: CNCF files a petition with the US Patent and Trademark Office to prevent Synadia from using the NATS logo and domain.
5. May 1, 2025: CNCF and Synadia reach an agreement that keeps NATS as an open source project within CNCF.

The Core Issues

The controversy centered around several key issues:

1. Trademark Ownership: Despite committing to transfer the NATS trademarks to the Linux Foundation, Synadia never completed this transfer and continued to claim ownership of the marks.
2. License Control: Synadia sought to change the project’s license from Apache 2.0 to BSL, which would have restricted commercial use and effectively ended NATS’ status as an open source project.
3. Infrastructure Control: Synadia demanded control of the nats.io domain and GitHub repositories, which CNCF had been managing since the project’s acceptance into CNCF.
4. Governance Process: Synadia-affiliated maintainers allegedly held a private vote to exit CNCF without engaging the broader contributor community.

The dispute highlighted a fundamental question: Can a company “take back” a project after donating it to a foundation? The CNCF’s position was clear – once donated, a project belongs to the community, not to any single entity, regardless of their continued contributions.

Implications for the COSS Landscape

The NATS controversy has several important implications for the commercial open source landscape:

1. The Value of Foundation Stewardship

The dispute underscores the critical role that foundations play in protecting open source projects from unilateral control. As CNCF’s blog post noted, “Open source foundations exist in part to protect the ecosystem from unilateral license changes and other vendor-driven rug-pulls.” Without this protection, companies might be tempted to leverage popular open source projects for short-term gain at the expense of long-term community trust.

2. The Importance of Clear Agreements

The delayed trademark transfer at the heart of the NATS controversy highlights the need for clear, enforceable agreements when projects are donated to foundations. While Synadia had committed to transferring the trademark, the delay created ambiguity that later contributed to the dispute. Foundations may need to strengthen their onboarding processes to ensure all legal requirements are met before projects are fully accepted.

3. The Tension Between Commercial Success and Open Governance

Synadia’s attempt to reclaim NATS reflects a broader tension in the COSS world: how can companies build sustainable businesses around open source projects while respecting community governance? As projects grow in popularity, the commercial incentives to exert greater control can increase, especially if companies feel they aren’t capturing sufficient value from their contributions.

4. The Power of Community Response

The resolution of the NATS dispute demonstrates the power of community pressure. As Derek Collison, CEO of Synadia, noted: “The outpouring of support from the global community over the past week for NATS to remain a thriving open source project with Synadia’s continued involvement has been extraordinary.” This community response likely played a significant role in bringing the parties back to the negotiating table.

The Role of Foundations in the COSS Ecosystem

The NATS controversy highlights several key roles that foundations play in the open source ecosystem:

1. Neutral Governance

Foundations provide neutral governance structures that prevent any single entity from dominating a project. This neutrality is essential for building trust among contributors and users, especially in competitive markets where multiple vendors might otherwise be reluctant to collaborate.

2. Legal Protection

Foundations offer legal protection for projects, including trademark management, license compliance, and sometimes patent protection. This legal infrastructure can be especially valuable for smaller projects that lack the resources to manage these issues independently.

3. Infrastructure Support

From hosting code repositories to managing domains and communication channels, foundations provide the infrastructure that keeps open source projects running smoothly. This support reduces the burden on individual contributors and ensures continuity even as maintainers come and go.

4. Community Building

Foundations help build and sustain communities around projects through events, marketing, and educational resources. These community-building efforts can significantly increase a project’s visibility and adoption, benefiting all stakeholders.

Lessons for Managing Foundation-Company Relationships

The NATS controversy offers several valuable lessons for both foundations and companies navigating these complex relationships:

For Foundations:

1. Enforce Clear Onboarding Requirements: Ensure all legal requirements, including trademark transfers, are completed before fully accepting projects.
2. Maintain Transparent Governance: Establish and enforce transparent governance processes that involve the broader community in major decisions.
3. Recognize Commercial Realities: Acknowledge the commercial interests of contributing companies. In formulating policies, strike a balance between ensuring openness and community-driven development and sensitivity to the business interests of commercial contributors.
4. Prepare for Disputes: Develop clear processes for handling disputes, including legal resources and community engagement strategies.

For Companies:

1. Understand the Commitment: Recognize that donating a project to a foundation means relinquishing certain controls, including the ability to unilaterally change licenses or governance.
2. Build Business Models Compatible with Open Governance: Design business strategies that can thrive within the constraints of open governance, rather than fighting against them.
3. Engage Honestly with the Community: Be transparent about commercial interests and work collaboratively with the community to address concerns.
4. Consider Alternative Approaches: If full project donation doesn’t align with business goals, consider alternative approaches like open core models or selective contribution.

Finding the Balance: A Path Forward

The resolution of the NATS controversy offers hope that even contentious disputes can be resolved in ways that benefit both companies and communities. The agreement reached between CNCF and Synadia preserves NATS as an open source project while acknowledging Synadia’s continued importance to its development.

This balanced approach points to a potential path forward for the COSS ecosystem: one where foundations provide the governance and infrastructure that keep projects open and accessible, while companies find sustainable ways to create and capture value within that framework.

As Todd Moore, SVP of Community Operations at the Linux Foundation, noted in the joint statement: “As steward of the NATS project, CNCF is committed to upholding open collaboration, neutral governance, and shared ownership so NATS can continue to grow and thrive as a community-driven project.

The NATS controversy may have been a moment of tension, but it also served as a valuable reminder of what makes open source powerful: the ability of diverse stakeholders to come together, work through differences, and create technology that benefits everyone. As the COSS landscape continues to evolve, maintaining this collaborative spirit will be essential for both foundations and the companies that support them.