An Open-Source Darling
To understand the drama, you first have to appreciate what Chef was. Founded in 2008, Chef became a cornerstone of the DevOps movement. It pioneered the concept of "infrastructure as code," allowing developers and system administrators to manage massive
server fleets not with manual clicks but with automated, repeatable scripts. For years, Chef operated on an "open core" model: the core software was free and open-source under the permissive Apache 2.0 license, while the company, Chef Software, Inc., sold proprietary enterprise features and support. This model fueled wide adoption, building a massive community that contributed code, wrote tutorials, and evangelized the product. Chef wasn't just a tool; it was a community-powered ecosystem.
The Business of Free
The open core model, however, has a fundamental tension: where do you draw the line between free and paid? As competitors like Ansible and Puppet gained ground and the market matured, Chef faced pressure to monetize its vast user base more effectively. The company had raised over $100 million in venture capital and needed to deliver a return. The balancing act between fostering an open community and building a sustainable commercial enterprise was becoming increasingly difficult. The desire for a clearer, more direct path to revenue set the stage for a monumental shift.
The Change That Broke the Community
In April 2019, Chef announced a radical change. It would no longer be "open core." Instead, all of its software, including previously proprietary enterprise features, would have its source code released under the Apache 2.0 license. It sounded like a win for open source, but there was a crucial catch: the pre-compiled, ready-to-use versions of the software (the "binaries") would now be distributed under a restrictive commercial end-user license agreement (EULA). In simple terms: the source code was free if you built it yourself, but using Chef's official product for commercial purposes now required a paid license. The company framed it as simplifying its model, similar to Red Hat's approach with Linux. But the community saw it as a betrayal. The trust that had been built over years—the social contract that users who contributed to the ecosystem would not suddenly be forced to pay for the tool they helped build—was shattered.
The Fork in the Road
The backlash was swift and decisive. Proving that the code was secondary to the license, a group of community members launched a project called Cinc. Pronounced "sink," Cinc is a clever acronym for "Cinc Is Not Chef." Its mission was simple: take the now fully open-source Chef code, compile it, and distribute free, community-supported binaries without the restrictive commercial EULA. It was a drop-in replacement. The existence of Cinc was the ultimate validation of the headline's premise. The community effectively said, "We love the code, but we reject your rules." They cloned the product but forked the philosophy.
A Cautionary Tale
The licensing change marked the beginning of the end for Chef as an independent market leader. While the company also faced unrelated controversies, such as a developer protest over a contract with ICE, the licensing decision alienated its core community. In October 2020, about a year and a half after the change, Chef was acquired by Progress Software for $220 million—a respectable sum, but a far cry from the valuations of its competitors. In the years since, Chef's market share has continued to consolidate around existing enterprise customers, while new projects often favor alternatives like Ansible or Terraform. The open-source Chef server is even being retired, with the Cinc project vowing to maintain it for the community.
