A
Argo CD
92.2
24,627 stars · Apache-2.0
DevOps
kestra leads by 3.0 · narrow
A
92.2
24,627 stars · Apache-2.0
B · leads
95.2
30,249 stars · Apache-2.0
Argo CD versus kestra is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Argo CD is written mainly in Go; kestra is written mainly in Java. The composite score is 92.2 for Argo CD and 95.2 for kestra.
kestra has 30,249 GitHub stars to Argo CD's 24,627, a gap of 5,622 (1.23×). Forks are 8,147 for Argo CD and 3,538 for kestra. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 91.
Push history: Argo CD was last pushed on 17 November 2026 (0 days ago), and kestra was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,489 for Argo CD (0.182 per star) and 651 for kestra (0.022 per star). Issue-health scores are 34 and 70; activity scores are 100 and 100.
Both Argo CD and kestra are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both Argo CD (24,627 stars) and kestra (30,249 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Argo CD is open source, kestra is open source.
The lead is split. Argo CD is furthest ahead on fork community (100 to 91), while kestra is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
kestra finishes ahead at 95.2 against Argo CD at 92.2, a 3.0 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Argo CD | kestra |
|---|---|---|
| GitHub stars | 24,627 | 30,249 |
| Forks | 8,147 | 3,538 |
| Open issues | 4,489 | 651 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 34 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.2 | 95.2 |
Argo CD is a GitOps continuous-delivery controller for Kubernetes. It watches Git and reconciles the cluster to the declared manifests.
Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.
kestra has more GitHub stars: 30,249 versus 24,627 for Argo CD. The gap is 5,622 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Argo CD and kestra as self-hostable. Confirm each project's deploy docs before you plan a migration.
Argo CD is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. kestra is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kestra scores 95.2 and Argo CD scores 92.2. This page calls that a narrow lead for kestra.