A
lens
76.2
23,248 stars · MIT
DevOps
unleash leads by 15.1 · decisive
A
76.2
23,248 stars · MIT
B · leads
91.3
14,330 stars · AGPL-3.0
lens versus unleash is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lens is written mainly in an unspecified language; unleash is written mainly in TypeScript. The composite score is 76.2 for lens and 91.3 for unleash.
lens has 23,248 GitHub stars to unleash's 14,330, a gap of 8,918 (1.62×). Forks are 1,466 for lens and 935 for unleash. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 94.
Push history: lens was last pushed on 11 February 2025 (644 days ago), and unleash was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,165 for lens (0.050 per star) and 48 for unleash (0.003 per star). Issue-health scores are 52 and 96; activity scores are 16 and 100.
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. unleash is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for lens and 52 for unleash. This is a procurement signal, not legal advice.
In DevOps, both lens (23,248 stars) and unleash (14,330 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: lens is open source, unleash is open source.
The lead is split. lens is furthest ahead on license flexibility (96 to 52), while unleash is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
unleash finishes ahead at 91.3 against lens at 76.2, a 15.1 point decisive 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 | lens | unleash |
|---|---|---|
| GitHub stars | 23,248 | 14,330 |
| Forks | 1,466 | 935 |
| Open issues | 1,165 | 48 |
| Adoption | 100 | 95 |
| Activity | 16 | 100 |
| Community | 100 | 94 |
| Issue health | 52 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 76.2 | 91.3 |
Lens - The way the world runs Kubernetes
Open-source feature management platform
lens has more GitHub stars: 23,248 versus 14,330 for unleash. The gap is 8,918 stars.
unleash was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.
Yes. This catalog marks both lens and unleash as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. unleash is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
unleash scores 91.3 and lens scores 76.2. This page calls that a decisive lead for unleash.