A · leads
dokploy
88.6
38,560 stars · license n/a
DevOps
dokploy leads by 15.3 · decisive
A · leads
88.6
38,560 stars · license n/a
B
73.3
23,248 stars · MIT
dokploy versus lens is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dokploy is written mainly in TypeScript; lens is written mainly in an unspecified language. The composite score is 88.6 for dokploy and 73.3 for lens.
dokploy has 38,560 GitHub stars to lens's 23,248, a gap of 15,312 (1.66×). Forks are 3,180 for dokploy and 1,466 for lens. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 90.
Push history: dokploy 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 833 for dokploy (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.
dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for dokploy and 96 for lens. This is a procurement signal, not legal advice.
In DevOps, both dokploy (38,560 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: dokploy is unpriced in this catalog, lens is open source.
The lead is split. dokploy is furthest ahead on recent activity (100 to 16), while lens is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
dokploy finishes ahead at 88.6 against lens at 73.3, a 15.3 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 | dokploy | lens |
|---|---|---|
| GitHub stars | 38,560 | 23,248 |
| Forks | 3,180 | 1,466 |
| Open issues | 833 | 1,165 |
| Adoption | 100 | 95 |
| Activity | 100 | 16 |
| Community | 100 | 90 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.6 | 73.3 |
Open Source Alternative to Vercel, Netlify and Heroku.
Lens - The way the world runs Kubernetes
dokploy has more GitHub stars: 38,560 versus 23,248 for lens. The gap is 15,312 stars.
dokploy was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.
Yes. This catalog marks both dokploy and lens as self-hostable. Confirm each project's deploy docs before you plan a migration.
dokploy is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
dokploy scores 88.6 and lens scores 73.3. This page calls that a decisive lead for dokploy.