Weaveworks is shutting down

Original Article ↗ Hacker News Discussion ↗

Weaveworks, a prominent player in the Kubernetes and cloud‑native ecosystem and creator of tools like FluxCD, Weave Net, eksctl, Cortex, and Ignite, is shutting down despite reportedly generating over $10M in annual revenue. Commenters see the failure as a case study in the difficulty of building sustainable, VC‑backed devtools businesses—especially when open source projects are widely adopted but hard to monetize—and in the risks of scaling headcount for “moonshot” growth rather than profitability. Many are concerned about the long‑term support of Weaveworks-backed projects but note that key efforts like FluxCD and Cilium (via its steward Isovalent) are under CNCF governance or other maintainers, while also reflecting more broadly on Kubernetes complexity, cloud‑native tooling economics, and the post–“free money” funding environment.

Company and Shutdown Context

  • Weaveworks provided Kubernetes-focused devops tooling and consulting: GitOps automation, networking (Weave Net), observability (Scope, Cortex), cluster tooling (eksctl, Ignite), etc.
  • The company reportedly had >$10M annual revenue and ~50–200 employees over time, but shut down after a last‑minute M&A deal fell through.
  • Many commenters see this as another example of a VC‑backed “grow fast or die” strategy: heavy burn after large rounds (~$36M of the ~$61M total), with little room to downshift into a smaller profitable business.
  • Debate over whether the board/leadership mismanaged cash vs. were constrained by VC incentives that strongly favor moonshots over modest, sustainable returns.

Open Source Projects and Future

  • Major OSS outputs: FluxCD, Flagger, Cortex, Weave Net, Weave Scope, eksctl, Ignite, grafanalib, and more.
  • FluxCD: described as a strong GitOps tool, often preferred over ArgoCD on technical grounds (Helm integration, lighter footprint). Criticism of the Flux v1→v2 migration as confusing and poorly handled.
  • Multiple comments stress Flux continues as a CNCF project with active maintainers now employed elsewhere; recent releases and an “enterprise distribution” effort are noted.
  • eksctl likely to remain healthy because it is the AWS‑endorsed tool for EKS and integrated into AWS docs.
  • Weave Net: mixed experiences. Some praise simplicity and encryption; others call it unreliable or criticize custom key exchange design. A maintained fork (“reweave”) is suggested.
  • Ignite and some other projects have already been archived.

Market, DevTools Economics, and Sales

  • Many argue devtools and cloud‑native infra startups are hard to monetize: developers avoid lock‑in and SaaS spend, and productivity gains are difficult to quantify.
  • Others note large successes (Atlassian, GitLab, MongoDB, Auth0, Snyk) but say you must be a broad platform or sell as “security,” not just productivity.
  • Critique of aggressive or poorly targeted sales (cold calls), with preference for product‑led, community‑driven adoption (HN, meetups, OSS reputation).

Cloud‑Native and Kubernetes Reflections

  • Some say the “cloud‑native balloon” has deflated and most orgs don’t need Kubernetes complexity; others see Kubernetes as “boring,” mature, and still gaining enterprise adoption.
  • Common pattern: managed Kubernetes + GitHub Actions + Helm is seen as sufficient; large ecosystems of add‑ons (ArgoCD, CNIs, operators) add complexity.
  • Weaveworks is cited as an example of strong technical contributions but a fragile business model around OSS infra tooling.