ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
A side-by-side editorial comparison of DNSControl and ElevenLabs — release velocity, themes, recent moves, and the top alternatives to consider.
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.
ElevenLabs is rebuilding voice agents as versioned software — branches, drafts, compiles, tests.
ElevenAgents now dominates the changelog, and it ships software-engineering primitives rather than voice features: branches, rebase, merge previews, drafts, and per-test tool mocks. Procedures compile into agent workflows, knowledge bases have crawl jobs and bulk operations, and telephony has widened past Twilio to Exotel and SIP. The speech and music models still advance — Music v2, Speech Engine — but they now read as components sitting under an agent runtime.
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.
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.
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.
ElevenAgents now dominates the changelog, and it ships software-engineering primitives rather than voice features: branches, rebase, merge previews, drafts, and per-test tool mocks. Procedures compile into agent workflows, knowledge bases have crawl jobs and bulk operations, and telephony has widened past Twilio to Exotel and SIP. The speech and music models still advance — Music v2, Speech Engine — but they now read as components sitting under an agent runtime.
The company is converging on an agent SDLC: author in a branch, hold changes as drafts, preview the merge, compile, then test against mocked tools. Every release adds another step of that loop rather than another voice. The analytics surface — sentiment scoring, termination reasons, backchannel flags, per-branch call volume — is being built to close the same loop with production evidence.
With simulations, tool mocks and is_error failure paths now in place alongside branches and merge previews, the missing piece is a gate: expect evaluation runs that block a branch merge on regression rather than leaving testing as a manual step.
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 ElevenLabs.
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
Nexus does the diagnosis; the rest is on-call plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
See all DNSControl alternatives → · See all ElevenLabs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ElevenLabs is currently shipping more aggressively (velocity 6.3 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ElevenLabs is currently shipping more aggressively (velocity 6.3 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.
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.
Top ElevenLabs alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ElevenLabs alternatives" section above for the current picks, or visit /alternatives/elevenlabs for the full list with editorial commentary on each.