A · level
infracost
92.6
12,622 stars · Apache-2.0
DevOps
Too close to call · 92.6 to 92.9
A · level
92.6
12,622 stars · Apache-2.0
B · level
92.9
26,788 stars · MIT
infracost versus jenkins is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. infracost is written mainly in Go; jenkins is written mainly in Java. The composite score is 92.6 for infracost and 92.9 for jenkins.
jenkins has 26,788 GitHub stars to infracost's 12,622, a gap of 14,166 (2.12×). Forks are 702 for infracost and 9,837 for jenkins. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 71 versus 100.
Push history: infracost was last pushed on 16 November 2026 (1 day ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4 for infracost (0.000 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 96 and 34; activity scores are 100 and 100.
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. jenkins 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. License scores in this pair are 96 for infracost and 96 for jenkins. This is a procurement signal, not legal advice.
In DevOps, both infracost (12,622 stars) and jenkins (26,788 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: infracost is open source, jenkins is open source.
The lead is split. infracost is furthest ahead on issue health (96 to 34), while jenkins is furthest ahead on fork community (100 to 71). Choose the dimension a rollout cannot compromise on.
Composite score: infracost 92.6, jenkins 92.9. 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.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | infracost | jenkins |
|---|---|---|
| GitHub stars | 12,622 | 26,788 |
| Forks | 702 | 9,837 |
| Open issues | 4 | 3,618 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 71 | 100 |
| Issue health | 96 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 92.9 |
Cloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!
Jenkins automation server
jenkins has more GitHub stars: 26,788 versus 12,622 for infracost. The gap is 14,166 stars.
jenkins was pushed more recently: 17 November 2026 versus 16 November 2026 for infracost. That is 1 days apart.
Yes. This catalog marks both infracost and jenkins as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. jenkins 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. infracost scores 92.6 and jenkins scores 92.9.