A · leads
kestra
96.5
30,249 stars · Apache-2.0
DevOps
kestra leads by 22.7 · decisive
A · leads
96.5
30,249 stars · Apache-2.0
B
73.8
23,248 stars · MIT
kestra versus lens is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kestra is written mainly in Java; lens is written mainly in an unspecified language. The composite score is 96.5 for kestra and 73.8 for lens.
kestra has 30,249 GitHub stars to lens's 23,248, a gap of 7,001 (1.30×). Forks are 3,538 for kestra and 1,466 for lens. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 89.
Push history: kestra 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 651 for kestra (0.022 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 70 and 52; activity scores are 100 and 16.
kestra 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 kestra and 96 for lens. This is a procurement signal, not legal advice.
In DevOps, both kestra (30,249 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: kestra is open source, lens is open source.
kestra is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 84 points (100 vs 16), and the tightest is self-hosting at 0 points (100 vs 100).
kestra finishes ahead at 96.5 against lens at 73.8, a 22.7 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 | kestra | lens |
|---|---|---|
| GitHub stars | 30,249 | 23,248 |
| Forks | 3,538 | 1,466 |
| Open issues | 651 | 1,165 |
| Adoption | 100 | 97 |
| Activity | 100 | 16 |
| Community | 100 | 89 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 73.8 |
Orchestrate everything, everywhere. The open-source control plane for workflows across data, infrastructure, business processes and AI agents. Declarative YAML, event-driven, any language, Git-versioned, scalable to millions of executions.
Lens - The way the world runs Kubernetes
kestra has more GitHub stars: 30,249 versus 23,248 for lens. The gap is 7,001 stars.
kestra was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.
Yes. This catalog marks both kestra and lens as self-hostable. Confirm each project's deploy docs before you plan a migration.
kestra 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.
kestra scores 96.5 and lens scores 73.8. This page calls that a decisive lead for kestra.