corednsvstrigger
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | trigger | |
|---|---|---|
| Score | 76/100 | 76/100 |
| Rank in category | #5 of 41 in DNS | #7 of 32 in Workflow Automation |
| GitHub stars | 14 400 | 16 644 |
| Stars, last 30 days | +60 | +257 |
| Stable releases, 12 months | 10 | 49 |
| Latest release | v1.15.0 · 21 Oct 2026 | v4.8.1 · 23 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Go | Typescript |
Which one should you pick?
coredns and trigger score the same (76/100), so the choice comes down to the details below.
trigger ships more often: 49 stable releases in the past year, against 10 for coredns.
If you want the quickest setup, coredns is easier to run; trigger needs more configuration.
trigger is growing faster right now (+257 stars in 30 days).
coredns details →trigger details →
Swap a project
Keep coredns, compare it with
Keep trigger, compare it with