A
gatus
89.7
12,813 stars · Apache-2.0
DevOps
kong leads by 8.2 · clear
A
89.7
12,813 stars · Apache-2.0
B · leads
97.9
44,388 stars · Apache-2.0
gatus versus kong 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; kong is written mainly in Lua. The composite score is 89.7 for gatus and 97.9 for kong.
kong has 44,388 GitHub stars to gatus's 12,813, a gap of 31,575 (3.46×). Forks are 918 for gatus and 5,242 for kong. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 80 versus 100.
Push history: gatus was last pushed on 16 November 2026 (1 day ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 446 for gatus (0.035 per star) and 233 for kong (0.005 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both gatus and kong 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 kong (44,388 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, kong is open source.
kong is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 20 points (80 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
kong finishes ahead at 97.9 against gatus at 89.7, a 8.2 point clear 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 | kong |
|---|---|---|
| GitHub stars | 12,813 | 44,388 |
| Forks | 918 | 5,242 |
| Open issues | 446 | 233 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.7 | 97.9 |
Automated developer-oriented status page with alerting and incident support
🦍 The API and AI Gateway
kong has more GitHub stars: 44,388 versus 12,813 for gatus. The gap is 31,575 stars.
kong 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 kong 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. kong 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.
kong scores 97.9 and gatus scores 89.7. This page calls that a clear lead for kong.