A
encore
87.4
12,720 stars · MPL-2.0
DevOps
jenkins leads by 5.5 · narrow
A
87.4
12,720 stars · MPL-2.0
B · leads
92.9
26,788 stars · MIT
encore versus jenkins is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. encore is written mainly in Go; jenkins is written mainly in Java. The composite score is 87.4 for encore and 92.9 for jenkins.
jenkins has 26,788 GitHub stars to encore's 12,720, a gap of 14,068 (2.11×). Forks are 660 for encore and 9,837 for jenkins. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 71 versus 100.
Push history: encore was last pushed on 13 November 2026 (4 days ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 154 for encore (0.012 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 84 and 34; activity scores are 92 and 100.
encore is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. jenkins 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 78 for encore and 96 for jenkins. This is a procurement signal, not legal advice.
In DevOps, both encore (12,720 stars) and jenkins (26,788 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: encore is open source, jenkins is open source.
The lead is split. encore is furthest ahead on issue health (84 to 34), while jenkins is furthest ahead on fork community (100 to 71). Choose the dimension a rollout cannot compromise on.
jenkins finishes ahead at 92.9 against encore at 87.4, a 5.5 point narrow 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 | encore | jenkins |
|---|---|---|
| GitHub stars | 12,720 | 26,788 |
| Forks | 660 | 9,837 |
| Open issues | 154 | 3,618 |
| Adoption | 93 | 100 |
| Activity | 92 | 100 |
| Community | 71 | 100 |
| Issue health | 84 | 34 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.4 | 92.9 |
Infrastructure orchestration from local to your cloud
Jenkins automation server
jenkins has more GitHub stars: 26,788 versus 12,720 for encore. The gap is 14,068 stars.
jenkins was pushed more recently: 17 November 2026 versus 13 November 2026 for encore. That is 4 days apart.
Yes. This catalog marks both encore and jenkins as self-hostable. Confirm each project's deploy docs before you plan a migration.
encore is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. jenkins 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.
jenkins scores 92.9 and encore scores 87.4. This page calls that a narrow lead for jenkins.