What Exactly is NATS.io?
Before diving into the drama, it helps to know what NATS is. Think of it as a universal remote for data. It’s a high-performance messaging system that lets different software components talk to each other instantly and reliably. Whether it's coordinating
microservices in the cloud, sending commands to a fleet of IoT devices, or streaming real-time financial data, NATS acts as the connective tissue. Created by Derek Collison, it’s known for being incredibly fast, lightweight, and resilient. Because of this, it has become a critical, if often invisible, piece of infrastructure for major companies in tech, finance, and logistics. It's open-source, managed under the umbrella of the Cloud Native Computing Foundation (CNCF), the same foundation that stewards massive projects like Kubernetes.
The Billion-Dollar Question: Open Source vs. Profit
The core of the disagreement boiled down to a classic conflict in the tech world: how do you keep a vital open-source project thriving financially? The primary corporate backer and maintainer of NATS is a company called Synadia, also founded by NATS creator Derek Collison. In early 2025, Synadia argued that it was funding nearly all (around 97%) of the development for NATS, while many large, profitable companies were using the technology for free without contributing back. Synadia felt that for the NATS ecosystem to flourish, Synadia itself had to thrive. This led them to a controversial decision: they wanted to change the licensing for the NATS server from the permissive Apache 2.0 to the more restrictive Business Source License (BSL). This new license would require companies using NATS commercially in certain ways to pay, ensuring a sustainable revenue stream to fund future development.
A Fight for Control
This proposed change in direction was a direct challenge to the CNCF's philosophy of vendor-neutral, freely available open source. The CNCF argued that Synadia had donated the project to the foundation in 2018 and couldn't unilaterally 'take it back' to commercialize it. The conflict escalated into a public battle. Synadia attempted to withdraw NATS from the foundation, a move the CNCF called an unprecedented 'takeover'. The leverage point in the dispute was the NATS trademark, which, due to a complex history, had never been formally transferred to the CNCF. Synadia asserted its ownership of the trademark to demand control over the project's domain name and code repositories. The open-source community watched as a project's corporate steward and its foundation home entered a high-stakes legal and philosophical standoff.
Resolution and the Path Forward
After intense public debate and community outcry, the standoff ended in May 2025. Synadia and the CNCF reached an agreement. NATS would remain an open source project within the CNCF, under its original Apache 2.0 license. In a key concession, Synadia agreed to continue its role as a major contributor and to finally transfer the trademark to the foundation, securing the project's vendor neutral future. While Synadia could still build commercial products 'on top' of NATS, the core project itself was guaranteed to remain open and free. The resolution was seen as a major win for the open source governance model, reaffirming that donated projects belong to the community, not just their original creators or primary funders.
