← Back to home
Comparison · Infra & APIs

DNSControl vs Quay

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

DNSControl vs Quay: at a glance

FeatureDNSControlQuay
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themesdns, infrastructure-as-code, devtools, release-candidatecontainer-registry, cve-remediation, ssrf-hardening, backports
Last editorial update2h ago7d 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 Quay?

Quay ships nothing but CVE remediation, mirrored across two supported branches

Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.

Read the full Quay trajectory →

DNSControl vs Quay: 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.

Q
Quay
INFRA · APIS
5.0

Quay ships nothing but CVE remediation, mirrored across two supported branches

◆ Current state

Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.

◆ Where it's heading

This is a registry in pure maintenance posture on its long-lived branches, with the release process itself automated down to changelog-bump commits. The recurring SSRF fixes across proxy cache and mirroring suggest a deliberate sweep through the code paths that fetch from upstream registries rather than isolated reports. Feature development, if it is happening, is landing on a branch this feed does not cover.

◆ Prediction

Expect the paired-branch cadence to continue at roughly the rate advisories land against the bundled Python and npm dependencies. The SSRF sweep looks close to complete, having now covered both proxy cache and mirroring.

Alternatives to DNSControl and Quay

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 Quay.

See all DNSControl alternatives → · See all Quay alternatives →

Recent activity from DNSControl and Quay

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

  1. 12h agoDNSControlDNSControl v5 rc9 sets a 25 August ship date, bugfixes only
  2. 6d agoDNSControlDNSControl v5 rc8 declared feature complete
  3. 7d agoQuayv3.12.21 patches six advisories and blocks SSRF in mirroring
  4. 7d agoQuayv3.10.25 carries the same advisory fixes to the 3.10 branch
  5. 16d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
  6. 17d agoDNSControlDNSControl v5 rc3 finishes converting every provider
  7. 27d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
  8. 27d agoQuayv3.12.20 bumps Go and blocks SSRF in proxy cache config
  9. 29d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
  10. 1mo agoQuayv3.10.24 backports the Go bump and proxy cache SSRF fix
  11. 1mo agoQuayv3.10.23 clears PyJWT, urllib3 and shell-quote advisories
  12. 1mo agoQuayv3.12.19 clears the same four dependency advisories

Frequently asked questions

What is the difference between DNSControl and Quay?

They serve adjacent needs but don't currently overlap on shipped themes. DNSControl and Quay are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is DNSControl better than Quay?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl and Quay are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Quay?

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