Skip to content
DevUtils Online

DevOps

dagger vs lens

dagger leads by 19.8 · decisive

A · leads

dagger

96.0

16,623 stars · Apache-2.0

B

lens

76.2

23,248 stars · MIT

dagger versus lens is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dagger is written mainly in Go; lens is written mainly in an unspecified language. The composite score is 96.0 for dagger and 76.2 for lens.

lens has 23,248 GitHub stars to dagger's 16,623, a gap of 6,625 (1.40×). Forks are 960 for dagger and 1,466 for lens. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 94 versus 100.

Push history: dagger was last pushed on 17 November 2026 (0 days ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 266 for dagger (0.016 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 84 and 52; activity scores are 100 and 16.

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

In DevOps, both dagger (16,623 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: dagger is open source, lens is open source.

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

dagger finishes ahead at 96.0 against lens at 76.2, a 19.8 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.

dagger versus lens metrics
Signal dagger lens
GitHub stars 16,623 23,248
Forks 960 1,466
Open issues 266 1,165
Adoption 97 100
Activity 100 16
Community 94 100
Issue health 84 52
License 96 96
Self-hosting 100 100
Composite 96.0 76.2

Questions this page answers

Which has more GitHub stars, dagger or lens?

lens has more GitHub stars: 23,248 versus 16,623 for dagger. The gap is 6,625 stars.

Which was updated more recently, dagger or lens?

dagger was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.

Can I self-host both dagger and lens?

Yes. This catalog marks both dagger 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, dagger or lens?

dagger 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 dagger vs lens score?

dagger scores 96.0 and lens scores 76.2. This page calls that a decisive lead for dagger.

Related comparisons