A
Argo CD
91.1
24,627 stars · Apache-2.0
DevOps
kong leads by 6.1 · narrow
A
91.1
24,627 stars · Apache-2.0
B · leads
97.2
44,388 stars · Apache-2.0
Argo CD versus kong 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; kong is written mainly in Lua. The composite score is 91.1 for Argo CD and 97.2 for kong.
kong has 44,388 GitHub stars to Argo CD's 24,627, a gap of 19,761 (1.80×). Forks are 8,147 for Argo CD and 5,242 for kong. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 100 versus 95.
Push history: Argo CD was last pushed on 17 November 2026 (0 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,489 for Argo CD (0.182 per star) and 233 for kong (0.005 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
Both Argo CD and kong 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 kong (44,388 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, kong is open source.
The lead is split. Argo CD is furthest ahead on fork community (100 to 95), while kong is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
kong finishes ahead at 97.2 against Argo CD at 91.1, a 6.1 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 | kong |
|---|---|---|
| GitHub stars | 24,627 | 44,388 |
| Forks | 8,147 | 5,242 |
| Open issues | 4,489 | 233 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.1 | 97.2 |
Argo CD is a GitOps continuous-delivery controller for Kubernetes. It watches Git and reconciles the cluster to the declared manifests.
🦍 The API and AI Gateway
kong has more GitHub stars: 44,388 versus 24,627 for Argo CD. The gap is 19,761 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Argo CD and kong 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. kong 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.
kong scores 97.2 and Argo CD scores 91.1. This page calls that a narrow lead for kong.