krakendvsMiddleware Manager
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| krakend | Middleware Manager | |
|---|---|---|
| Score | 63/100 | 49/100 |
| Rank in category | #10 of 38 in API Gateway | #16 of 23 in Reverse Proxy |
| GitHub stars | 2 704 | 516 |
| Stars, last 30 days | +13 | +4 |
| Stable releases, 12 months | 18 | 8 |
| Latest release | v3.0.4 · 12 Nov 2026 | v4.5.0 · 24 Mar 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Go |
Which one should you pick?
krakend scores 63/100 against 49/100 for Middleware Manager, so it is the safer default.
krakend ships more often: 18 stable releases in the past year, against 8 for Middleware Manager.
If you want the quickest setup, krakend is easier to run; Middleware Manager needs more configuration.
krakend is growing faster right now (+13 stars in 30 days).
Key differences
- License: krakend is Apache-2.0, Middleware Manager is MIT.
- Features only krakend lists: API aggregation and composition, Automatic content encoding conversion, Backend response caching, Circuit Breaker and 9 more.
- Features only Middleware Manager lists: Custom Service Definitions, Dual data source support, Forward authentication integration, Health check endpoint and 5 more.
- Both offer: Rate Limiting.
krakend details →Middleware Manager details →