head to head · open source
cloudflared vs coredns
cloudflared has 16,673 GitHub stars, 1,544 forks, 545 open issues and last shipped 4 days ago. coredns has 14,444 stars, 2,572 forks, 282 open issues and last shipped 2 days ago. cloudflared leads on adoption by 15% (16,673 vs 14,444 stars). cloudflared is written in Go under Apache-2.0; coredns is written in Go under Apache-2.0. cloudflared has attracted 9% as many forks as stars, coredns 18%. coredns was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| cloudflared | coredns | |
|---|---|---|
| GitHub stars | ★ 17K | ★ 14K |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Go | Go |
| Last push | 2026-11-17 | 2026-11-19 |
| Forks | ⑂ 1.5K | ⑂ 2.6K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick cloudflared if
- You weight community size — 17K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick coredns if
- You want the coredns feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and coredns fits your workflow better
About cloudflared
Cloudflare Tunnel client Contains the command line client for Cloudflare Tunnel, a tunneling daemon that proxies traffic from the Cloudflare network to your origins. This daemon sits between Cloudflare network and your origin (e.g. a webserver). Cloudflare attracts client requests and sends them to you via this daemon, without requiring you to poke holes on your firewall your origin can remain as closed as possible. Extensive documentation can be found in the Cloudflare Tunnel section of the Cloudflare Docs. All usages related with proxying to your origins are available under cloudflared tunnel help . You can…
read the full cloudflared overview →
About coredns
CoreDNS is a DNS server/forwarder, written in Go, that chains plugins. Each plugin performs a (DNS) function. CoreDNS is a Cloud Native Computing Foundation graduated project. CoreDNS is a fast and flexible DNS server. The key word here is flexible : with CoreDNS you are able to do what you want with your DNS data by utilizing plugins. If some functionality is not provided out of the box you can add it by writing a plugin. CoreDNS can listen for DNS requests coming in over: UDP/TCP (go'old DNS). TLS DoT (RFC 7858). DNS over HTTP/2 DoH (RFC 8484). DNS over HTTP/3 DoH3 DNS over QUIC DoQ (RFC 9250). gRPC (not a…
read the full coredns overview →
More in Infrastructure & Operations
Related comparisons
More Networking & Connectivity projects
Compare either of these against the rest of the Networking & Connectivity field.
Frequently asked questions
Is cloudflared or coredns more popular?
cloudflared has 16,673 GitHub stars and coredns has 14,444. cloudflared has the larger community by that measure.
Are cloudflared and coredns free?
Both are open source. cloudflared is licensed under Apache-2.0 and coredns under Apache-2.0. Neither carries a licence fee.
What is the difference between cloudflared and coredns?
cloudflared is written in Go and coredns in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, cloudflared or coredns?
Choose cloudflared if you want the larger community (16,673 stars) or its Apache-2.0 licence terms. Choose coredns if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.