A
90DaysOfDevOps
71.6
30,916 stars · license n/a
DevOps
Argo CD leads by 20.6 · decisive
A
71.6
30,916 stars · license n/a
B · leads
92.2
24,627 stars · Apache-2.0
90DaysOfDevOps versus Argo CD is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. 90DaysOfDevOps is written mainly in Shell; Argo CD is written mainly in Go. The composite score is 71.6 for 90DaysOfDevOps and 92.2 for Argo CD.
90DaysOfDevOps has 30,916 GitHub stars to Argo CD's 24,627, a gap of 6,289 (1.26×). Forks are 6,812 for 90DaysOfDevOps and 8,147 for Argo CD. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 98 versus 100.
Push history: 90DaysOfDevOps was last pushed on 24 June 2026 (146 days ago), and Argo CD was last pushed on 17 November 2026 (0 days ago). Open issues stand at 12 for 90DaysOfDevOps (0.000 per star) and 4,489 for Argo CD (0.182 per star). Issue-health scores are 96 and 34; activity scores are 36 and 100.
90DaysOfDevOps is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for 90DaysOfDevOps and 96 for Argo CD. This is a procurement signal, not legal advice.
Only Argo CD is marked self-hostable here (24,627 stars, deploy score 100). 90DaysOfDevOps is not (30,916 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: 90DaysOfDevOps is unpriced in this catalog, Argo CD is open source.
The lead is split. 90DaysOfDevOps is furthest ahead on issue health (96 to 34), while Argo CD is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Argo CD finishes ahead at 92.2 against 90DaysOfDevOps at 71.6, a 20.6 point decisive 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 | 90DaysOfDevOps | Argo CD |
|---|---|---|
| GitHub stars | 30,916 | 24,627 |
| Forks | 6,812 | 8,147 |
| Open issues | 12 | 4,489 |
| Adoption | 100 | 98 |
| Activity | 36 | 100 |
| Community | 98 | 100 |
| Issue health | 96 | 34 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 71.6 | 92.2 |
This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.
Argo CD is a GitOps continuous-delivery controller for Kubernetes. It watches Git and reconciles the cluster to the declared manifests.
90DaysOfDevOps has more GitHub stars: 30,916 versus 24,627 for Argo CD. The gap is 6,289 stars.
Argo CD was pushed more recently: 17 November 2026 versus 24 June 2026 for 90DaysOfDevOps. That is 146 days apart.
Only Argo CD is marked self-hostable. 90DaysOfDevOps is not.
90DaysOfDevOps is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
Argo CD scores 92.2 and 90DaysOfDevOps scores 71.6. This page calls that a decisive lead for Argo CD.