A
infracost
91.8
12,622 stars · Apache-2.0
DevOps
kong leads by 6.1 · narrow
A
91.8
12,622 stars · Apache-2.0
B · leads
97.9
44,388 stars · Apache-2.0
infracost versus kong 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; kong is written mainly in Lua. The composite score is 91.8 for infracost and 97.9 for kong.
kong has 44,388 GitHub stars to infracost's 12,622, a gap of 31,766 (3.52×). Forks are 702 for infracost and 5,242 for kong. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 76 versus 100.
Push history: infracost was last pushed on 16 November 2026 (1 day ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4 for infracost (0.000 per star) and 233 for kong (0.005 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both infracost and kong 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 infracost (12,622 stars) and kong (44,388 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, kong is open source.
The lead is split. infracost is furthest ahead on issue health (96 to 84), while kong is furthest ahead on fork community (100 to 76). Choose the dimension a rollout cannot compromise on.
kong finishes ahead at 97.9 against infracost at 91.8, a 6.1 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 | infracost | kong |
|---|---|---|
| GitHub stars | 12,622 | 44,388 |
| Forks | 702 | 5,242 |
| Open issues | 4 | 233 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 76 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.8 | 97.9 |
Cloud cost intelligence for engineers, AI coding agents, and CI/CD 💰📉 Shift FinOps Left!
🦍 The API and AI Gateway
kong has more GitHub stars: 44,388 versus 12,622 for infracost. The gap is 31,766 stars.
kong 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 kong 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. kong 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.
kong scores 97.9 and infracost scores 91.8. This page calls that a narrow lead for kong.