Chef's Open Source ModelĪlthough Chef has always billed itself as an open source company, until early last year it primarily employed an "open core" model in which enterprise-focused proprietary applications added functionality to its open source tools.Īt November's KubeCon Kubernetes conference in San Diego, Chef CTO Corey Scobie told Data Center Knowledge that until April 2019, when it open sourced its entire portfolio, its licensing varied from project to project. "This acquisition perfectly aligns with our growth strategy and meets the requirements that we’ve previously laid out: a strong recurring revenue model, technology that complements our business, a loyal customer base, and the ability to leverage our operating model and infrastructure to run the business more efficiently," Yogesh Gupta, Progress's CEO, said in a statement. Progress will inherit Chef's staff, which includes developers familiar with the territory covered by both companies.Ĭhef's customer base - which includes the likes of Facebook, IBM, SAP, Alaska Airlines, and Capital One - brings in more than $70 million in annual recurring revenue. The bacon and eggs analogy actually runs deeper and covers more than merely the two companies' complementary software offerings. "At the same time, Chef fills a need in the Progress portfolio in DevSecOps, infrastructure, application, and compliance automation that is highly complementary to its existing products." "Chef and Progress share a vision for the future of DevSecOps, and Progress will provide the scale to further drive Chef’s platform forward and deliver additional value to our customers," Barry Crist, Chef's CEO, said in a statement when the sale was announced. While Progress is strong on the developer side of the DevOps model, Chef's strength is on the operations side. Chef has a line of complementary software for automating and helping companies manage their software. Progress's backbone is a platform for developing and deploying business applications that is heavily used in enterprise data centers. We do know that the two companies' products go together like bacon and eggs. We won't know much about publicly traded Progress's post acquisition plans until the deal closes (expected in October), but it's a good bet that Progress will end up open sourcing at least some of its own proprietary offerings after the ink has dried. In case you missed the news, last week Bedford, Massachusetts-based Progress announced it's acquiring the 10-year-old Seattle-based IT infrastructure automation startup for $220 million cash.
We won't know until until the deal closes, but one consequence of Chef's pending takeover by Progress might mean there will be more open source software headed for the data center.
0 kommentar(er)
