Skip to content
DevUtils Online

DevOps

infracost vs lens

infracost leads by 19.4 · decisive

A · leads

infracost

95.6

12,622 stars · Apache-2.0

B

lens

76.2

23,248 stars · MIT

infracost versus lens 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; lens is written mainly in an unspecified language. The composite score is 95.6 for infracost and 76.2 for lens.

lens has 23,248 GitHub stars to infracost's 12,622, a gap of 10,626 (1.84×). Forks are 702 for infracost and 1,466 for lens. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 90 versus 100.

Push history: infracost was last pushed on 16 November 2026 (1 day ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 4 for infracost (0.000 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 96 and 52; activity scores are 100 and 16.

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. lens 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 lens. This is a procurement signal, not legal advice.

In DevOps, both infracost (12,622 stars) and lens (23,248 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, lens is open source.

The lead is split. infracost is furthest ahead on recent activity (100 to 16), while lens is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.

infracost finishes ahead at 95.6 against lens at 76.2, a 19.4 point decisive margin under the published weights.

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.

infracost versus lens metrics
Signal infracost lens
GitHub stars 12,622 23,248
Forks 702 1,466
Open issues 4 1,165
Adoption 94 100
Activity 100 16
Community 90 100
Issue health 96 52
License 96 96
Self-hosting 100 100
Composite 95.6 76.2

Questions this page answers

Which has more GitHub stars, infracost or lens?

lens has more GitHub stars: 23,248 versus 12,622 for infracost. The gap is 10,626 stars.

Which was updated more recently, infracost or lens?

infracost was pushed more recently: 16 November 2026 versus 11 February 2025 for lens. That is 643 days apart.

Can I self-host both infracost and lens?

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

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

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

Who wins the infracost vs lens score?

infracost scores 95.6 and lens scores 76.2. This page calls that a decisive lead for infracost.

Related comparisons