homarr-iframesvskrakend
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| homarr-iframes | krakend | |
|---|---|---|
| Score | 46/100 | 63/100 |
| Rank in category | #27 of 44 in Dashboard | #10 of 38 in API Gateway |
| GitHub stars | 123 | 2 704 |
| Stars, last 30 days | +0 | +13 |
| Stable releases, 12 months | 0 | 18 |
| Latest release | — | v3.0.4 · 12 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Go | Go |
Which one should you pick?
krakend scores 63/100 against 46/100 for homarr-iframes, so it is the safer default.
krakend ships more often: 18 stable releases in the past year, against 0 for homarr-iframes.
krakend is growing faster right now (+13 stars in 30 days).
Key differences
- License: homarr-iframes is MIT, krakend is Apache-2.0.
- Platforms only homarr-iframes lists: Build from Source.
- Platforms only krakend lists: AWS, Debian, Homebrew, Linux.
- Features only homarr-iframes lists: Alarms dashboard, Configurable via Environment Variables, Embeddable iFrames, Multi-source Aggregation and 2 more.
- Features only krakend lists: API aggregation and composition, Automatic content encoding conversion, Backend response caching, Circuit Breaker and 10 more.
homarr-iframes details →krakend details →
Swap a project
Keep homarr-iframes, compare it with
Keep krakend, compare it with