cloudflare-tunnel-ingress-controllervsDockFlare
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| cloudflare-tunnel-ingress-controller | DockFlare | |
|---|---|---|
| Score | 55/100 | 57/100 |
| Rank in category | #5 of 7 in Kubernetes | #12 of 23 in Reverse Proxy |
| GitHub stars | 1 207 | 2 505 |
| Stars, last 30 days | +4 | +15 |
| Stable releases, 12 months | 3 | 10 |
| Latest release | v0.1.0 · 12 Aug 2026 | v3.1.6 · 20 Sept 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | GPL-3.0 |
| Main language | Go | Python |
Which one should you pick?
DockFlare scores 57/100 against 55/100 for cloudflare-tunnel-ingress-controller, so it is the safer default.
DockFlare ships more often: 10 stable releases in the past year, against 3 for cloudflare-tunnel-ingress-controller.
DockFlare is growing faster right now (+15 stars in 30 days).
Key differences
- License: cloudflare-tunnel-ingress-controller is MIT, DockFlare is GPL-3.0.
- Language: cloudflare-tunnel-ingress-controller is written mainly in Go, DockFlare in Python.
- Platforms only cloudflare-tunnel-ingress-controller lists: Helm.
- Platforms only DockFlare lists: Linux.
- Features only cloudflare-tunnel-ingress-controller lists: Automatic DNS record management, Automatic tunnel provisioning, Bring-your-own credentials Secret, High Availability and 3 more.
- Features only DockFlare lists: Cloudflare Zero Trust Access policy management, Encrypted backup and restore, Graceful deletion with configurable grace period, Label-driven Cloudflare Tunnel and DNS provisioning and 8 more.
cloudflare-tunnel-ingress-controller details →DockFlare details →
Swap a project
Keep cloudflare-tunnel-ingress-controller, compare it with
Keep DockFlare, compare it with