ConvoyvsKong Gateway
Two self-hosted API Gateway projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Convoy | Kong Gateway | |
|---|---|---|
| Score | 61/100 | 81/100 |
| Rank in category | #12 of 38 in API Gateway | #1 of 38 in API Gateway |
| GitHub stars | 2 891 | 44 383 |
| Stars, last 30 days | +13 | +124 |
| Stable releases, 12 months | 30 | 3 |
| Latest release | v26.9.5 · 12 Nov 2026 | 3.9.4 · 12 Oct 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | Elastic-2.0 | Apache-2.0 |
| Main language | Go | Lua |
Which one should you pick?
Kong Gateway scores 81/100 against 61/100 for Convoy, so it is the safer default.
Convoy ships more often: 30 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
- License: Convoy is Elastic-2.0, Kong Gateway is Apache-2.0.
- Language: Convoy is written mainly in Go, Kong Gateway in Lua.
- Platforms only Convoy lists: Docker.
- Platforms only Kong Gateway lists: Kubernetes.
- Features only Convoy lists: Automatic Retries, Batch retries, Circuit Breaking, Dynamic endpoints and 10 more.
- Features only Kong Gateway lists: Authentication & Authorization, Declarative Configuration, Hybrid Deployment, Logging & Monitoring and 6 more.
- Both offer: Rate Limiting.
Convoy details →Kong Gateway details →All API Gateway projects →