ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
Comparison · Infra & APIs
DNSControl vs Vault
A side-by-side editorial comparison of DNSControl and Vault — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl vs Vault: at a glance
What is DNSControl?
DNSControl is rewriting its record internals in public, one release candidate at a time
DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.
What is Vault?
Vault under IBM lands 2.0.0, with FIPS 140-3 and HSM enterprise builds inside two weeks.
Vault crossed 2.0.0 in late March under its post-HashiCorp / IBM stewardship — the artifact pages now carry IBM's International Program License Agreement language alongside the existing MPL 2.0 / BSL terms. Enterprise variants followed within days: 2.0.0 enterprise FIPS 140-3 and HSM-flavored builds published April 1 and April 8, plus an sdk/v0.25.1 backport addressing a Go CVE. The recent shipping is release-engineering-heavy, not feature-heavy.
DNSControl vs Vault: editorial side-by-side
DNSControl
5.0INFRA · APIS
DNSControl is rewriting its record internals in public, one release candidate at a time
◆ Current state
DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.
◆ Where it's heading
The stated goals are about future velocity rather than present features: making new DNS record types faster to adopt and custom record types easier to implement. That is a bet that the bottleneck on supporting new record types was the internal representation, and it is being paid for with a long candidate series rather than a big-bang release. The provider conversion finished during this window — rc3 declares all providers converted with long-tail work remaining — so the refactor is past its riskiest stretch.
◆ Prediction
The maintainer states v5.x is on schedule to ship before September, and the untested-provider list is the visible blocker; expect further candidates focused on provider coverage rather than new goals.
Vault
2.5INFRA · APISDEVOPS
Vault under IBM lands 2.0.0, with FIPS 140-3 and HSM enterprise builds inside two weeks.
◆ Current state
Vault crossed 2.0.0 in late March under its post-HashiCorp / IBM stewardship — the artifact pages now carry IBM's International Program License Agreement language alongside the existing MPL 2.0 / BSL terms. Enterprise variants followed within days: 2.0.0 enterprise FIPS 140-3 and HSM-flavored builds published April 1 and April 8, plus an sdk/v0.25.1 backport addressing a Go CVE. The recent shipping is release-engineering-heavy, not feature-heavy.
◆ Where it's heading
This is the cadence of a project completing a major-version rollout — community GA first, then RC and GA enterprise-flavor builds, then security-tracking SDK backports — rather than a roadmap pivot. The fact that FIPS 140-3 and HSM enterprise builds shipped in the same window as the 2.0 cycle is the signal worth holding onto: Vault's federal and regulated-industry posture is being kept intact under the new owner, and auth plugin version bumps suggest the wider ecosystem is staying in step.
◆ Prediction
Expect 2.x feature-bearing minor releases over the next few months, with FIPS 140-3 and HSM enterprise variants tracked alongside the community builds. GA bumps for the auth plugins to match the 2.x line are likely. Worth watching for more visible IBM branding or any Cloud-side packaging shifts that signal repositioning under the new owner.
Alternatives to DNSControl and Vault
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 Vault.
Honeycomb
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
GitHub
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
incident.io
Nexus does the diagnosis; the rest is on-call plumbing
werf
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
See all DNSControl alternatives → · See all Vault alternatives →
Recent activity from DNSControl and Vault
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
- 10d agoDNSControlDNSControl v5 rc3 finishes converting every provider
- 19d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
- 22d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
- 4mo agoVaultVault 2.0.0 Enterprise FIPS 140-3 build available
- 4mo agoVaultSDK 0.25.1 backports CVE-2026-34986 Go fix
- 4mo agoVaultVault 2.0.0 RC1 Enterprise HSM build
- 4mo agoVaultVault 2.0.0 RC1 release-artifacts PR
- 4mo agoVaultVault 2.0.0 Enterprise HSM + FIPS 140-3 build
- 4mo agoVaultVault 2.0.0 RC1 Enterprise HSM + FIPS 140-3 build
Frequently asked questions
What is the difference between DNSControl and Vault?
They serve adjacent needs but don't currently overlap on shipped themes. DNSControl is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Vault?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Vault?
Top Vault alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Vault alternatives" section above for the current picks, or visit /alternatives/vault for the full list with editorial commentary on each.