A
gatus
90.5
12,813 stars · Apache-2.0
DevOps
jenkins leads by 2.4 · narrow
A
90.5
12,813 stars · Apache-2.0
B · leads
92.9
26,788 stars · MIT
gatus versus jenkins is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. gatus is written mainly in Go; jenkins is written mainly in Java. The composite score is 90.5 for gatus and 92.9 for jenkins.
jenkins has 26,788 GitHub stars to gatus's 12,813, a gap of 13,975 (2.09×). Forks are 918 for gatus and 9,837 for jenkins. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 74 versus 100.
Push history: gatus was last pushed on 16 November 2026 (1 day ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 446 for gatus (0.035 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.
gatus 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. 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 96 for gatus and 96 for jenkins. This is a procurement signal, not legal advice.
In DevOps, both gatus (12,813 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: gatus is open source, jenkins is open source.
The lead is split. gatus is furthest ahead on issue health (70 to 34), while jenkins is furthest ahead on fork community (100 to 74). Choose the dimension a rollout cannot compromise on.
jenkins finishes ahead at 92.9 against gatus at 90.5, a 2.4 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 | gatus | jenkins |
|---|---|---|
| GitHub stars | 12,813 | 26,788 |
| Forks | 918 | 9,837 |
| Open issues | 446 | 3,618 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.5 | 92.9 |
Automated developer-oriented status page with alerting and incident support
Jenkins automation server
jenkins has more GitHub stars: 26,788 versus 12,813 for gatus. The gap is 13,975 stars.
jenkins was pushed more recently: 17 November 2026 versus 16 November 2026 for gatus. That is 1 days apart.
Yes. This catalog marks both gatus and jenkins as self-hostable. Confirm each project's deploy docs before you plan a migration.
gatus 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. 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 gatus scores 90.5. This page calls that a narrow lead for jenkins.