Overview

Flux has been an open-source, vendor-neutral CNCF project since 2016 and is now CNCF Graduated. It keeps Kubernetes clusters reconciled with declared configuration, including resources for infrastructure and workloads. That makes it a strong option for teams building a delivery workflow around Git and Kubernetes rather than seeking a standalone deployment service.

Approval gates and rollback support give teams control over changes, while built-in dependency management helps coordinate infrastructure and workloads. The trade-off is operational: installation requires cluster-admin rights, and older end-of-life Kubernetes versions are not supported. The project does not provide its own UI, so teams wanting a first-party visual interface should look elsewhere or consider third-party ecosystem UIs.

Key features

Reconciliation and deployment sources

Flux automatically reconciles clusters against sources such as Git repositories, OCI artifacts, Helm repositories and S3-compatible buckets. It works with GitHub, GitLab and Bitbucket, as well as container registries, Helm and Kustomize. Multiple repositories and multi-cluster management help platform teams apply a consistent approach across environments; Kubernetes RBAC impersonation supports multi-tenancy.

Progressive delivery and image automation

With Flagger, Flux supports canary deployments, feature flags and A/B rollouts. It can also scan container images and commit automated image updates back to Git. These capabilities suit teams that want progressive changes and image updates within their Kubernetes delivery workflow, rather than a basic sync-only controller.

Security and policy

Flux integrates with OPA, Kyverno and admission controllers for policy validation. Its CLI and controller images are signed with Sigstore Cosign and GitHub OIDC and published with signatures on GitHub Container Registry and Docker Hub. Controller deployments conform to the Kubernetes restricted pod security standard, including non-root execution and a read-only root filesystem. Security work includes audits in 2021 and 2023 and a 2025 TAG Security self-assessment; vulnerability handling is best effort.

Notifications and support

Flux can alert external systems, including chat tools such as Slack, when configuration is synced and ready. Community interaction runs through GitHub Discussions, Slack and a mailing list. Volunteer maintenance keeps the project vendor-neutral, but the project itself does not provide 24/7 support or SLAs. Commercial vendors such as ControlPlane offer those services, along with hardened images and private consulting.

Pricing

Flux — 0.00 USD per free. The open-source Kubernetes delivery project has no paid project plan or free trial. It requires a Kubernetes cluster, and older end-of-life Kubernetes versions are unsupported. This is a practical fit for teams able to operate the software themselves; organizations that need contractual support should budget for a commercial provider.

Platforms

Flux is self-hosted and targets Kubernetes clusters, Git repositories, OCI artifact registries and Helm repositories. Its CLI is available for Linux, macOS and Windows, with installation methods documented for all three. The listed minimum supported Kubernetes versions begin at v1.34.1 for the v1.34 series, and installation requires cluster-admin access.

Who it's for

Flux fits Kubernetes operators and platform teams that want declarative delivery, multi-cluster management and integrations with existing Git, Helm, Kustomize and policy tooling. Application developers can also use it within a continuous delivery practice. It is a weaker fit for teams without cluster-admin access, those seeking a built-in UI, or organizations that require project-backed service levels rather than community channels or a commercial support arrangement.

Pros and cons

Pros: Git-based reconciliation supports multiple source types and multi-cluster workflows, making it useful for teams standardizing Kubernetes delivery.
Pros: Flagger rollouts, image automation, dependency management, approval gates and rollback cover more than basic configuration syncing.
Pros: Signed images, restricted pod security practices and policy integrations provide concrete security controls for platform operators.
Cons: Cluster-admin installation rights and a Kubernetes cluster are prerequisites, limiting adoption where teams cannot control cluster setup.
Cons: No project-provided UI means teams need to be comfortable with CLI-led operation or select a third-party interface.
Cons: Volunteer maintenance and best-effort vulnerability handling may not meet requirements for guaranteed support; commercial support is separate.

Alternatives

Choose Argo CD if you want another free, self-managed GitOps delivery option for Kubernetes. Consider PipeCD for an Apache 2.0 open-source alternative.

GoCD is a free, downloadable open-source continuous delivery server, while AWS CodePipeline offers a freemium pipeline model with a V2 plan billed per action execution minute after 100 free action execution minutes per month. For mobile-focused build workflows, Bitrise, Codemagic and Appcircle have plans centered on build credits or build-minute and concurrency limits. Octopus Deploy is another freemium deployment option with machine and tenant add-ons.

Verdict

Choose Flux if your team already runs Kubernetes and wants open, extensible GitOps delivery with progressive rollout and image automation capabilities. Its strongest reason to choose is the breadth of Kubernetes-native workflow integrations at no project plan cost. Look elsewhere if you need a first-party UI, cannot grant cluster-admin rights or require guaranteed support directly from the project.

	Flux CD	Helm
Free plan	Yes	Yes
Free trial	No	No
Paid from	Free	Free
Open source	No	No
Platforms	api, Linux, macOS, self-hosted, Windows	Linux, macOS, Windows
Free plan	Yes	Yes
Helm support	—	Yes
Deployment model	—	self_hosted
Audit logs	—	Yes

Flux CD vs Helm

Flux CD

Helm