A · leads
Argo CD
92.9
24,627 stars · Apache-2.0
DevOps
Argo CD leads by 2.0 · narrow
A · leads
92.9
24,627 stars · Apache-2.0
B
90.9
12,813 stars · Apache-2.0
Argo CD versus gatus 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 92.9 for Argo CD and 90.9 for gatus.
Argo CD has 24,627 GitHub stars to gatus's 12,813, a gap of 11,814 (1.92×). Forks are 8,147 for Argo CD and 918 for gatus. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 76.
Push history: Argo CD was last pushed on 17 November 2026 (0 days ago), and gatus was last pushed on 16 November 2026 (1 day ago). Open issues stand at 4,489 for Argo CD (0.182 per star) and 446 for gatus (0.035 per star). Issue-health scores are 34 and 70; activity scores are 100 and 100.
Both Argo CD and gatus 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 gatus (12,813 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, gatus is open source.
The lead is split. Argo CD is furthest ahead on fork community (100 to 76), while gatus is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
Argo CD finishes ahead at 92.9 against gatus at 90.9, a 2.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 | gatus |
|---|---|---|
| GitHub stars | 24,627 | 12,813 |
| Forks | 8,147 | 918 |
| Open issues | 4,489 | 446 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 34 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 90.9 |
Argo CD is a GitOps continuous-delivery controller for Kubernetes. It watches Git and reconciles the cluster to the declared manifests.
Automated developer-oriented status page with alerting and incident support
Argo CD has more GitHub stars: 24,627 versus 12,813 for gatus. The gap is 11,814 stars.
Argo CD was pushed more recently: 17 November 2026 versus 16 November 2026 for gatus. That is 1 days apart.
Yes. This catalog marks both Argo CD and gatus 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. gatus 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.
Argo CD scores 92.9 and gatus scores 90.9. This page calls that a narrow lead for Argo CD.