Kong Gatewayvskrakend
Two self-hosted API Gateway projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Kong Gateway | krakend | |
|---|---|---|
| Score | 81/100 | 63/100 |
| Rank in category | #1 of 38 in API Gateway | #10 of 38 in API Gateway |
| GitHub stars | 44 383 | 2 704 |
| Stars, last 30 days | +124 | +13 |
| Stable releases, 12 months | 3 | 18 |
| Latest release | 3.9.4 · 12 Oct 2026 | v3.0.4 · 12 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Lua | Go |
Which one should you pick?
Kong Gateway scores 81/100 against 63/100 for krakend, so it is the safer default.
krakend ships more often: 18 stable releases in the past year, against 3 for Kong Gateway.
Kong Gateway is growing faster right now (+124 stars in 30 days).
Key differences
- Language: Kong Gateway is written mainly in Lua, krakend in Go.
- Platforms only Kong Gateway lists: Kubernetes, Kubernetes (Helm).
- Platforms only krakend lists: AWS, Debian, Docker, Homebrew and 1 more.
- Features only Kong Gateway lists: Authentication & Authorization, Declarative Configuration, Hybrid Deployment, Logging & Monitoring and 6 more.
- Features only krakend lists: API aggregation and composition, Automatic content encoding conversion, Backend response caching, Circuit Breaker and 9 more.
- Both offer: Rate Limiting.
Kong Gateway details →krakend details →All API Gateway projects →