Weaveworks Shuts Down: What It Means for GitOps and the Future of Flux
Weaveworks, the company that coined the term GitOps, announced its closure due to unstable sales despite $10 million revenue, prompting industry analysis of GitOps’s commercial viability, competition with ArgoCD, and the future stewardship of the open‑source Flux project under CNCF.
Weaveworks, the company that coined the term "GitOps," announced its imminent shutdown, stating that although its revenue exceeded $10 million, sales growth was unstable and a long‑term investor was needed, leading to the company being positioned for acquisition.
Prior to this, Weaveworks had acquired another continuous delivery (CD) company, Armory, and the intellectual property and technology are now owned by Harness, which builds its software delivery platform on the open‑source Spinnaker project.
OpsMx CEO Gopal Dommety commented that while Weaveworks was one of the founders of the idea, GitOps is still the correct answer for fast, automated, flexible, and secure software delivery and operations.
Gartner research VP Paul Delory said the industry "thanks them for creating this category" but "it clearly has not translated into commercial success," attributing this to two main reasons: Flux, the Kubernetes‑focused open‑source CD solution sponsored by Weaveworks, faces fierce competition from another GitOps project, ArgoCD, which many find simpler to use, and the overall market for GitOps products appears limited despite the hype.
Delory added that the free open‑source market for GitOps tools makes it difficult to sell commercial solutions, as lengthy, high‑touch sales cycles and uncertainty about who within an IT organization has budget authority further complicate funding, especially as venture capital becomes harder to secure.
Regarding the future of the open‑source Flux project, CNCF CTO Chris Aniszcyk explained that many Flux maintainers have been hired by other companies but will continue their work, and CNCF will coordinate with member companies to support the project if it faces forks or a lack of maintainers. Richardson also noted on LinkedIn that he is working directly with several large organizations to ensure Flux’s continuity.
"The story does not end here—our open‑source software is everywhere," Richardson said.
DevOps Cloud Academy
Exploring industry DevOps practices and technical expertise.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.