Skip to content
DevUtils Online

DevOps

Argo CD vs infracost

Too close to call · 92.9 to 93.1

A · level

Argo CD

92.9

24,627 stars · Apache-2.0

B · level

infracost

93.1

12,622 stars · Apache-2.0

Argo CD versus infracost 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 93.1 for infracost.

Argo CD has 24,627 GitHub stars to infracost's 12,622, a gap of 12,005 (1.95×). Forks are 8,147 for Argo CD and 702 for infracost. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 73.

Push history: Argo CD was last pushed on 17 November 2026 (0 days ago), and infracost was last pushed on 16 November 2026 (1 day ago). Open issues stand at 4,489 for Argo CD (0.182 per star) and 4 for infracost (0.000 per star). Issue-health scores are 34 and 96; activity scores are 100 and 100.

Both Argo CD and infracost 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 infracost (12,622 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, infracost is open source.

The lead is split. Argo CD is furthest ahead on fork community (100 to 73), while infracost is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.

Composite score: Argo CD 92.9, infracost 93.1. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Argo CD versus infracost metrics
Signal Argo CD infracost
GitHub stars 24,627 12,622
Forks 8,147 702
Open issues 4,489 4
Adoption 100 93
Activity 100 100
Community 100 73
Issue health 34 96
License 96 96
Self-hosting 100 100
Composite 92.9 93.1

Argo CD

Argo CD is a GitOps continuous-delivery controller for Kubernetes. It watches Git and reconciles the cluster to the declared manifests.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Argo CD or infracost?

Argo CD has more GitHub stars: 24,627 versus 12,622 for infracost. The gap is 12,005 stars.

Which was updated more recently, Argo CD or infracost?

Argo CD was pushed more recently: 17 November 2026 versus 16 November 2026 for infracost. That is 1 days apart.

Can I self-host both Argo CD and infracost?

Yes. This catalog marks both Argo CD and infracost as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Argo CD or infracost?

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. infracost 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.

Who wins the Argo CD vs infracost score?

Neither tool clears a one-point margin. Argo CD scores 92.9 and infracost scores 93.1.

Related comparisons