Skip to content
DevUtils Online

DevOps

gatus vs witr

Too close to call · 94.5 to 94.0

A · level

gatus

94.5

12,813 stars · Apache-2.0

B · level

witr

94.0

23,030 stars · Apache-2.0

gatus versus witr is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 94.5 for gatus and 94.0 for witr.

witr has 23,030 GitHub stars to gatus's 12,813, a gap of 10,217 (1.80×). Forks are 918 for gatus and 811 for witr. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 100 versus 98.

Push history: gatus was last pushed on 16 November 2026 (1 day ago), and witr was last pushed on 23 October 2026 (25 days ago). Open issues stand at 446 for gatus (0.035 per star) and 8 for witr (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 78.

Both gatus and witr are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In DevOps, both gatus (12,813 stars) and witr (23,030 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, witr is open source.

The lead is split. gatus is furthest ahead on recent activity (100 to 78), while witr is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.

Composite score: gatus 94.5, witr 94.0. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

gatus versus witr metrics
Signal gatus witr
GitHub stars 12,813 23,030
Forks 918 811
Open issues 446 8
Adoption 94 100
Activity 100 78
Community 100 98
Issue health 70 96
License 96 96
Self-hosting 100 100
Composite 94.5 94.0

Questions this page answers

Which has more GitHub stars, gatus or witr?

witr has more GitHub stars: 23,030 versus 12,813 for gatus. The gap is 10,217 stars.

Which was updated more recently, gatus or witr?

gatus was pushed more recently: 16 November 2026 versus 23 October 2026 for witr. That is 24 days apart.

Can I self-host both gatus and witr?

Yes. This catalog marks both gatus and witr as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, gatus or witr?

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. witr 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the gatus vs witr score?

Neither tool clears a one-point margin. gatus scores 94.5 and witr scores 94.0.

Related comparisons