← Back to home
Comparison · Infra & APIs

DNSControl vs Spacelift

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

DNSControl vs Spacelift: at a glance

FeatureDNSControlSpacelift
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesdns, infrastructure-as-code, devtools, release-candidateiac, agentic-deploys, mcp, policy-governance
Last editorial update3h ago13d 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 Spacelift?

Spacelift's AI stopped explaining infrastructure and started deploying it.

The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.

Read the full Spacelift trajectory →

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

S
Spacelift
INFRA · APIS
0.0

Spacelift's AI stopped explaining infrastructure and started deploying it.

◆ Current state

The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.

◆ Where it's heading

The arc is easy to trace: Intent opened to everyone in December, Intelligence launched in March, an MCP server exposed the platform to outside assistants in May, and by July the AI is performing deployments rather than describing them. Running underneath is the governance work that makes that defensible — module sharing permissions, OIDC claims, SCIM — because an agent that can deploy is only sellable if the registry and the identity provider bound what it can reach. Terragrunt support and the plan-policy cleanup show the core IaC engine still being maintained rather than neglected for the AI work.

◆ Prediction

Deployment by name is the narrow case; the obvious next step is Intent handling multi-stack changes with policy checks in the loop, and the permission model being extended to describe what the AI specifically is allowed to deploy rather than what a user is.

Alternatives to DNSControl and Spacelift

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

See all DNSControl alternatives → · See all Spacelift alternatives →

Recent activity from DNSControl and Spacelift

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

  1. 13h agoDNSControlDNSControl v5 rc9 sets a 25 August ship date, bugfixes only
  2. 6d agoDNSControlDNSControl v5 rc8 declared feature complete
  3. 14d agoSpaceliftAPI will return HTTP 500 on internal errors instead of 200
  4. 16d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
  5. 17d agoDNSControlDNSControl v5 rc3 finishes converting every provider
  6. 27d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
  7. 29d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
  8. 1mo agoSpaceliftAsk Spacelift Intelligence to deploy a module by name
  9. 2mo agoSpaceliftSCIM provisioning available in Spacelift!
  10. 2mo agoSpaceliftLearning Certificates now available in Spacelift!
  11. 3mo agoSpaceliftAnnouncing the Spacelift Remote MCP Server!
  12. 4mo agoSpaceliftLaunchpad Learn: Structured hands-on training for Spacelift

Frequently asked questions

What is the difference between DNSControl and Spacelift?

They serve adjacent needs but don't currently overlap on shipped themes. DNSControl is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Spacelift?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Spacelift?

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