What it does
Kargo is an open-source continuous-promotion tool for moving software artifacts and desired configuration through stages such as test and production. It complements Argo CD: Kargo coordinates promotion by committing changes to Git, while a GitOps agent such as Argo CD reconciles the desired state to a Kubernetes cluster. The project is self-hosted in a Kubernetes environment and is not itself the deployment controller.
Promote a change by changing Git state
Kargo's quickstart creates a local Kubernetes environment, installs Kargo with Helm, and uses a demo configuration repository. The documented prerequisites include Helm 3.13.1 or newer; the quickstart installs cert-manager, Argo CD, and Kargo. Kargo needs a Git repository it can push to, so the tutorial asks the user to fork a demo repository and provide a token with write access. In a real project, scope that permission to the configuration repository rather than reusing a broad personal token.
The useful first task is to promote a built image from a test stage to the next stage. Kargo records the desired manifest change in Git; an agent such as Argo CD applies the updated desired state to the cluster. The FAQ draws a clear boundary: Kargo handles continuous promotion, while the GitOps agent performs the actual deployment. Any commands in the upstream quickstart are setup examples, not commands run for this listing.
Operational and licensing boundaries
Kargo is an upstream Apache-2.0 project, and its FAQ points to a separate commercial distribution and professional support from Akuity. The upstream software therefore has an established open-source license, but this record does not imply that commercial support or a hosted offering has the same price or terms. Self-hosting also means the operator must maintain the Kubernetes environment, Git credentials, and any GitOps controller used for deployment.
Strengths
- Makes promotion through application lifecycle stages an explicit workflow instead of hiding every transition in custom scripts.
- Writes promoted configuration to Git so an existing GitOps agent can reconcile the updated desired state.
- The upstream repository publishes an Apache License 2.0.
Watch out for
- A working installation requires a Kubernetes environment and Helm; the documented setup also uses Git repository write access.
- Kargo promotes desired state but relies on a separate GitOps agent, such as Argo CD, to perform deployment.
Best for
- Kubernetes teams promoting container or configuration changes across test, staging, and production stages.
- GitOps workflows that should record promotions as changes to a configuration repository.
- Teams already using Argo CD that want a separate control plane for the progression of changes.
Sources
- Kargo (Oct 25, 2026)
- Kargo Quickstart | Kargo Docs (Oct 25, 2026)
- Frequently Asked Questions | Kargo Docs (Oct 25, 2026)
- kargo/LICENSE at main · akuity/kargo · GitHub (Oct 25, 2026)