Flux Review, Pricing & Features

Flux (FluxCD) is a CNCF Graduated, open source GitOps tool for Kubernetes. See its GitOps Toolkit architecture, pricing, pros, cons, and Argo CD alternatives.

Category
DevOps
Pricing
Open Source (optional paid Enterprise support add-on), from Free
Verified
Not yet
Last updated
July 18, 2026
Founded
2016
Free PlanAPIOpen SourceFreemiumSelf-Hosted

Overview

Flux, also known as FluxCD, is a CNCF Graduated, open source GitOps continuous delivery tool for Kubernetes. It continuously compares the live state of a cluster against a desired state declared in Git, Helm repositories, or OCI artifacts, and automatically reconciles any drift, so that Git effectively becomes the single, auditable source of truth for everything running on the cluster.

The project was originally created by Weaveworks, the London-based company that coined the term 'GitOps' in 2017, and was later fully rewritten as a modular set of Kubernetes controllers called the GitOps Toolkit, released as Flux v2. Flux graduated within the CNCF on November 30, 2022, becoming the 18th project to reach that highest maturity tier. After Weaveworks shut down in February 2024, the Kubernetes security consultancy ControlPlane hired several of the project's core maintainers to keep development and commercial support alive.

Key Features

Flux's functionality is delivered through independent GitOps Toolkit controllers: source-controller acquires content from Git, OCI, Helm, and bucket sources; kustomize-controller and helm-controller apply Kustomize manifests and Helm charts respectively; notification-controller handles alerting and webhook receivers; and the image-reflector-controller and image-automation-controller together detect new container image tags and commit updated references back to Git automatically.

Because each controller is a discrete Kubernetes operator with its own Custom Resource Definitions, teams can install only the components they need, keeping the resource footprint small. Flux supports multi-tenancy through Kubernetes RBAC impersonation, works across multi-cluster and multi-cloud fleets alongside Cluster API, and pairs with the companion Flagger project to enable progressive delivery patterns such as canary releases, blue-green deployments, and automated rollback based on metrics.

Pricing

The core Flux project is entirely free and open source under the Apache 2.0 license, with no feature gating, seat limits, or usage caps for self-hosted deployments. Support for the free tier comes from the community through GitHub Discussions, a CNCF Slack workspace, and public maintainer meetings.

The only paid offering sits on top of the free project: ControlPlane sells an annual 'Enterprise for Flux CD' subscription that bundles a commercially licensed, hardened version of the Flux Operator with vendor SLAs and professional services, priced on a custom basis per organization rather than published tiers. Revenue from that subscription is used to directly fund the maintainers who continue developing the open source project.

Key Features

Pros & Cons

Pros

  • Fully free, Apache 2.0 licensed core with no paywalled features or usage limits for self-hosted use
  • Lightweight, independently-composable controller architecture that keeps resource usage small, favoring edge and resource-constrained clusters
  • CNCF Graduated status backed by a broad, vendor-neutral maintainer community rather than a single company
  • Deep native integration with Kustomize, Helm, and Kubernetes RBAC without requiring a separate application layer or database

Cons

  • No built-in web UI in the core project, so visual, single pane of glass management requires separate third-party tooling
  • Steeper initial learning curve than dashboard-first tools for teams that expect an out-of-the-box graphical interface
  • Weaveworks, the project's original commercial backer, shut down in 2024, which briefly created uncertainty about long-term enterprise support until ControlPlane stepped in
  • Smaller name recognition and marketing presence among application developers compared with Argo CD, which ships a more polished default UI

Pricing

Frequently Asked Questions

What is Flux (FluxCD) used for?

Flux is used to continuously deploy and manage Kubernetes applications and cluster configuration using GitOps: it watches Git, Helm, or OCI sources and automatically reconciles the cluster to match the declared desired state.

Is Flux free to use?

Yes. The core Flux project and all GitOps Toolkit controllers are open source under the Apache 2.0 license and free to self-host with no seat or usage limits. An optional paid ControlPlane Enterprise subscription adds vendor support and a hardened Flux Operator.

Did the Weaveworks shutdown affect the Flux project?

Weaveworks, the company that originally created Flux and coined the term GitOps, shut down in February 2024. Flux itself was unaffected because it is governed independently by the CNCF, and ControlPlane subsequently hired several of the former core maintainers, including Stefan Prodan, to continue the project.

What is the difference between Flux and Argo CD?

Both are CNCF Graduated GitOps tools, but Argo CD typically runs as a centralized control plane with a full web UI and single sign-on, while Flux runs as a decentralized set of lightweight controllers inside each cluster, favoring a smaller footprint, CLI and API-driven workflows, and no mandatory central dashboard.

What is the GitOps Toolkit?

The GitOps Toolkit is the set of composable Kubernetes controllers that make up Flux v2, including source-controller, kustomize-controller, helm-controller, notification-controller, image-reflector-controller, and image-automation-controller, each exposing its own Custom Resource Definitions.

Is Flux a CNCF Graduated project?

Yes. Flux graduated within the Cloud Native Computing Foundation on November 30, 2022, becoming the 18th project to reach Graduated maturity, the foundation's highest level of project trust and stability.

Comparisons

Related Tools