Kluctl is a declarative deployment tool for Kubernetes built around the concept of a deployment project — a directory tree of Kustomize bases, Helm charts, and Jinja2-templated manifests that describes an entire environment. Unlike most GitOps tools, it is designed to be run interactively from a terminal as well as from a controller.
A Kluctl project defines targets (clusters/environments) and renders the same base deployment differently per target through variable sources pulled from Git, files, or env vars. The kluctl diff and kluctl deploy commands show you exactly which resources will change before you apply them, with a tree-structured diff that distinguishes between new, changed, orphaned, and hook resources. Pruning is explicit: Kluctl tracks previously applied resources via labels and asks before deleting orphans. A flux-style controller is available for GitOps mode, but many users stick with the CLI workflow because the diff-first UX is the point.
It overlaps with Flux, Argo CD, Helmfile, and raw Kustomize. Kluctl’s niche is teams who want Helm+Kustomize composition plus templating plus a proper local diff/apply loop without committing to a full GitOps controller.