A
encore
86.6
12,720 stars · MPL-2.0
DevOps
kong leads by 11.3 · clear
A
86.6
12,720 stars · MPL-2.0
B · leads
97.9
44,388 stars · Apache-2.0
encore versus kong 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; kong is written mainly in Lua. The composite score is 86.6 for encore and 97.9 for kong.
kong has 44,388 GitHub stars to encore's 12,720, a gap of 31,668 (3.49×). Forks are 660 for encore and 5,242 for kong. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 76 versus 100.
Push history: encore was last pushed on 13 November 2026 (4 days ago), and kong was last pushed on 17 November 2026 (0 days ago). Open issues stand at 154 for encore (0.012 per star) and 233 for kong (0.005 per star). Issue-health scores are 84 and 84; 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. 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. License scores in this pair are 78 for encore and 96 for kong. This is a procurement signal, not legal advice.
In DevOps, both encore (12,720 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: encore is open source, kong is open source.
kong is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is fork community at 24 points (76 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
kong finishes ahead at 97.9 against encore at 86.6, a 11.3 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 | encore | kong |
|---|---|---|
| GitHub stars | 12,720 | 44,388 |
| Forks | 660 | 5,242 |
| Open issues | 154 | 233 |
| Adoption | 88 | 100 |
| Activity | 92 | 100 |
| Community | 76 | 100 |
| Issue health | 84 | 84 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.6 | 97.9 |
Infrastructure orchestration from local to your cloud
🦍 The API and AI Gateway
kong has more GitHub stars: 44,388 versus 12,720 for encore. The gap is 31,668 stars.
kong 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 kong 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. 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 encore scores 86.6. This page calls that a clear lead for kong.