corednsvsmultiwoven
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | multiwoven | |
|---|---|---|
| Score | 76/100 | 57/100 |
| Rank in category | #5 of 41 in DNS | #4 of 8 in Data Pipeline |
| GitHub stars | 14 398 | 1 683 |
| Stars, last 30 days | +55 | +5 |
| Stable releases, 12 months | 10 | 26 |
| Latest release | v1.15.0 · 21 Oct 2026 | v0.136.0 · 20 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | No |
| License | Apache-2.0 | AGPL-3.0 |
| Main language | Go | Ruby |
Which one should you pick?
coredns scores 76/100 against 57/100 for multiwoven, so it is the safer default.
multiwoven ships more often: 26 stable releases in the past year, against 10 for coredns.
If you want the quickest setup, coredns is easier to run; multiwoven needs more configuration.
coredns is growing faster right now (+55 stars in 30 days).
coredns details →multiwoven details →
Swap a project
Keep coredns, compare it with
Keep multiwoven, compare it with