Weaveworks’ closure has thrown the state of GitOps into flux.

0

Advertisement: Click here to learn how to Generate Art From Text

Weaveworks will soon cease to exist. The company that coined GitOps is no more. The company’s CEO Alexis Richardson wrote in a LinkedIn postThe company shut down earlier this week. 

According to Richardson, while the company was bringing in over $10 million in revenue, the sales growth wasn’t consistent. The company needed a longer-term investor and was about to be acquired when the deal fell apart. 

The following follows the Recent acquisitionHarness now owns the intellectual property and technology of Armory, another CD company. 

Gopal Dommety said that even though Weaveworks had been one of its originators, the idea has now spread across the industry. 

“GitOps is still the right answer for fast, automated, flexible, and secure software delivery and operations,” he said. 

According to Paul Delory, research vice president at Gartner, the industry is “indebted to them for creating this category,” but “clearly that didn’t translate to commercial success.”

Delory attributes it to two main factors. Weaveworks sponsored Flux, an open-source Kubernetes CD solution. However, it was facing stiff competition from another open source GitOps. ArgoCD

“I feel like there was much more interest in ArgoCD of late, which is simpler to use … Functionality-wise, there’s much less daylight between the two products than there used to be,” he said.

Second, it’s possible there’s just not a commercial market for GitOps, even though there’s a lot of hype around this. There are many reasons for this, such as that it’s mainly limited for use with Kubernetes, there is a long setup process before GitOps can even be up and running, and there’s also confusion about who to sell GitOps products to: developers, IT teams, platforms teams, etc. 

Delory believes that, in general, the open-source GitOps market makes it difficult to justify purchasing a commercial tool. 

“Even if an IT organization is amenable to your sales pitch, you’re still looking at a long, high-touch sales process while you figure out who in a particular IT organization has the desire and the budget to sign the contract,” he said. “That makes a steady stream of venture capital even more critical, while you wait out these long sales cycles. But VC funding is hard to come by at the moment. As Alexis alluded to in his blog post, Weaveworks couldn’t get its hands on enough capital to sustain itself while its technology and sales efforts came to fruition.”

Weaveworks contributed heavily to the Flux open-source project. Many people are wondering what this means for the future. 

Chris Aniszcyk is the CTO of CNCF, the current home of the Flux project. He says that many Flux maintainers are already employed by other companies, and will continue to work on the project. 

“CNCF will do our best to notify our member companies to pitch-in when it comes to these situations like we have in the past,” he said. “The CNCF Technical Oversight Committee (TOC) reviews the health of projects often and in cases where a project is forked or is lacking maintainers, we work with our member community. Grafana forked the Cortex project a few years ago and maintained were moved to that project. CNCF made a call to our members to see if folks can help and AWS and Red Hat stepped in.”

Richardson also said in his LinkedIn post that he was working directly with “several large organizations” to ensure the future of Flux. 

“The story does not end here – our open source software is used everywhere,” Richardson said. 

 

Leave a Reply

Your email address will not be published. Required fields are marked *