A · leads
act
97.0
72,721 stars · MIT
DevOps
act leads by 7.4 · clear
A · leads
97.0
72,721 stars · MIT
B
89.6
24,627 stars · Apache-2.0
act versus Argo CD is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 97.0 for act and 89.6 for Argo CD.
act has 72,721 GitHub stars to Argo CD's 24,627, a gap of 48,094 (2.95×). Forks are 2,126 for act and 8,147 for Argo CD. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 85 versus 100.
Push history: act was last pushed on 16 November 2026 (1 day ago), and Argo CD was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 4,489 for Argo CD (0.182 per star). Issue-health scores are 96 and 34; activity scores are 100 and 100.
act is listed as MIT, 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. 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. License scores in this pair are 96 for act and 96 for Argo CD. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and Argo CD (24,627 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: act is open source, Argo CD is open source.
The lead is split. act is furthest ahead on issue health (96 to 34), while Argo CD is furthest ahead on fork community (100 to 85). Choose the dimension a rollout cannot compromise on.
act finishes ahead at 97.0 against Argo CD at 89.6, a 7.4 point clear 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 | act | Argo CD |
|---|---|---|
| GitHub stars | 72,721 | 24,627 |
| Forks | 2,126 | 8,147 |
| Open issues | 318 | 4,489 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 96 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.0 | 89.6 |
Run your GitHub Actions locally 🚀
Argo CD is a GitOps continuous-delivery controller for Kubernetes. It watches Git and reconciles the cluster to the declared manifests.
act has more GitHub stars: 72,721 versus 24,627 for Argo CD. The gap is 48,094 stars.
Argo CD was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.
Yes. This catalog marks both act and Argo CD as self-hostable. Confirm each project's deploy docs before you plan a migration.
act is listed as MIT, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
act scores 97.0 and Argo CD scores 89.6. This page calls that a clear lead for act.