// the find
weaveworks/weave-gitops
Weave GitOps is transitioning to a community driven project! It provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.
Weave GitOps is a UI and CLI layer on top of Flux that gives teams a dashboard for viewing and managing GitOps deployments without needing deep Kubernetes expertise. It's aimed at platform engineers who want to expose Flux's reconciliation state to developers who shouldn't need to kubectl their way around. Weaveworks (the company) went bust in 2024, and the project is now trying to survive as a community effort.
The cluster manager abstraction (core/clustersmngr) handles multi-cluster auth and client pooling in a way that's actually thought through — delegating cache, per-cluster RBAC, not just a map of kubeconfigs. The gRPC + grpc-gateway API design (api/core/core.proto) means you get HTTP and gRPC from one definition, which is the right call for a project that needs both a UI and a CLI. The ADR directory (doc/adr/) has 16 documented decisions with real tradeoffs explained, which is rarer than it should be. Test coverage uses counterfeiter fakes rather than hand-rolled mocks, so interface changes break tests immediately.
The elephant in the room: Weaveworks folded in early 2024 and the 'transitioning to community driven' framing in the description is doing a lot of work. 1,123 stars and 166 forks after years of corporate backing is a thin community to sustain a project this large. The enterprise features (pipelines, CAPI, Terraform controller) lived in a closed-source enterprise tier that's now gone, leaving gaps in the OSS version that contributors will need to fill or drop. The repo primary language shows as MDX, meaning the docs site outweighs the actual Go code in line count — not a great sign for a developer tool. Multi-cluster support requires the enterprise controller that no longer exists in maintained form, so anyone running more than one cluster hits a wall fast.