← Back to home
Comparison · Infra & APIs

DNSControl vs Windmill

A side-by-side editorial comparison of DNSControl and Windmill — release velocity, themes, recent moves, and the top alternatives to consider.

DNSControl vs Windmill: at a glance

FeatureDNSControlWindmill
SectorInfra & APIsInfra & APIs
Velocity score5.08.8
Sparks · 30d01
Top themesdns, infrastructure-as-code, devtools, release-candidateworkflow orchestration, dbt, open core, ai sessions
Last editorial update3h ago1d ago
WebsiteVisit →Visit →

What is DNSControl?

DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup

DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.

Read the full DNSControl trajectory →

What is Windmill?

Windmill gave away the warehouse connectors and now runs dbt natively — the trial is the strategy.

Two lines are moving at once. The platform line made dbt projects a first-class runtime, unified the deployment target on workspace lineage, opened Compare & Deploy to arbitrary target workspaces, and moved BigQuery and Snowflake out from behind the Enterprise license. The AI line took sessions to beta on by default and has been adding controls around them since — file attachments, visible web-search sources, artifact version history, and now a read-only plan mode that refuses anything that writes or deploys until you approve a plan.

Read the full Windmill trajectory →

DNSControl vs Windmill: editorial side-by-side

D
DNSControl
INFRA · APIS
5.0

DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup

◆ Current state

DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.

◆ Where it's heading

The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.

◆ Prediction

Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.

W
Windmill
INFRA · APIS
8.8

Windmill gave away the warehouse connectors and now runs dbt natively — the trial is the strategy.

◆ Current state

Two lines are moving at once. The platform line made dbt projects a first-class runtime, unified the deployment target on workspace lineage, opened Compare & Deploy to arbitrary target workspaces, and moved BigQuery and Snowflake out from behind the Enterprise license. The AI line took sessions to beta on by default and has been adding controls around them since — file attachments, visible web-search sources, artifact version history, and now a read-only plan mode that refuses anything that writes or deploys until you approve a plan.

◆ Where it's heading

Windmill is positioning as the place a data team's existing work already runs rather than a system to be ported to: an unmodified dbt project drops in, its models become addressable assets with ref() lineage, and the warehouse languages needed to reach them are no longer paywalled. In parallel, the AI session work is maturing from capability to governance — the recent additions are all about reviewability and constraint, not raw autonomy. The deployment changes point the same way, collapsing configurable targets into a single derived answer.

◆ Prediction

Expect the plan-and-approve posture to spread beyond session chats into the durable AI surfaces, and more warehouse-adjacent runtimes to follow dbt into the first-class treatment; Oracle and MS SQL remain the obvious Enterprise holdouts to watch.

Alternatives to DNSControl and Windmill

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either DNSControl or Windmill.

See all DNSControl alternatives → · See all Windmill alternatives →

Recent activity from DNSControl and Windmill

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 13h agoDNSControlDNSControl v5 rc9 sets a 25 August ship date, bugfixes only
  2. 5d agoWindmillPlan mode for AI sessions
  3. 6d agoDNSControlDNSControl v5 rc8 declared feature complete
  4. 8d agoWindmillNested filter groups and dotted paths in trigger filters
  5. 9d agoWindmillVersion history for AI session artifacts
  6. 16d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
  7. 17d agoDNSControlDNSControl v5 rc3 finishes converting every provider
  8. 18d agoWindmillRun dbt projects as a first-class Windmill runtime
  9. 20d agoWindmillOne deployment target, derived from the workspace lineage
  10. 20d agoWindmillCompare & Deploy into any workspace
  11. 27d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
  12. 29d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor

Frequently asked questions

What is the difference between DNSControl and Windmill?

They serve adjacent needs but don't currently overlap on shipped themes. Windmill is currently shipping more aggressively (velocity 8.8 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is DNSControl better than Windmill?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Windmill is currently shipping more aggressively (velocity 8.8 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to DNSControl?

Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.

What are the best alternatives to Windmill?

Top Windmill alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Windmill alternatives" section above for the current picks, or visit /alternatives/windmill for the full list with editorial commentary on each.