ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
Comparison · Infra & APIs
DNSControl vs Knock
A side-by-side editorial comparison of DNSControl and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl vs Knock: at a glance
| Feature | DNSControl | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | dns, infrastructure-as-code, refactor, release-candidates | notification-infrastructure, data-sources, agent-native, workflow-orchestration |
| Last editorial update | 12h ago | 4d ago |
| Website | Visit → | — |
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 Knock?
Knock is wiring both ends of the messaging data loop, then putting an agent on top
Knock has spent the last month building around its notification engine rather than inside it. Two new inbound data sources, Amplitude and Clay, let product events, cohorts, and enriched account rows land in Knock without customers writing sync code, while message and engagement events flow back out to the warehouse. The dashboard work alongside it, a rebuilt template editor, saved views and tags, schema management, and passkeys, reads as hardening for teams rather than individual developers.
DNSControl vs Knock: 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.
Knock
6.3INFRA · APIS
Knock is wiring both ends of the messaging data loop, then putting an agent on top
◆ Current state
Knock has spent the last month building around its notification engine rather than inside it. Two new inbound data sources, Amplitude and Clay, let product events, cohorts, and enriched account rows land in Knock without customers writing sync code, while message and engagement events flow back out to the warehouse. The dashboard work alongside it, a rebuilt template editor, saved views and tags, schema management, and passkeys, reads as hardening for teams rather than individual developers.
◆ Where it's heading
The direction is away from a notification API you call and toward the system that holds the messaging state. Ingesting cohort membership and enriched contact data is CDP-adjacent territory, and the wait-for-event function turns linear sequences into event-driven orchestration. The Knock agent then adds a natural-language layer over performance data, so the platform answers questions instead of only exporting rows.
◆ Prediction
Expect more data sources on the same pattern, warehouse and CRM-side connectors that keep audiences in sync without customer glue code. Whether the agent moves from reading analytics to editing workflows directly is the open question these entries do not yet answer.
Alternatives to DNSControl and Knock
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 Knock.
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 Knock alternatives →
Recent activity from DNSControl and Knock
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6d agoKnockAmplitude data source
- 8d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
- 10d agoDNSControlDNSControl v5 rc3 finishes converting every provider
- 13d agoKnockAnalytics in the Knock agent ⚡
- 14d agoKnockWait for event function
- 15d agoKnockClay data source
- 19d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
- 20d agoKnockRedesigned template editor
- 22d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
- 27d agoKnockBranch rebasing
Frequently asked questions
What is the difference between DNSControl and Knock?
They serve adjacent needs but don't currently overlap on shipped themes. Knock 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.
Is DNSControl better than Knock?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock 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.
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 Knock?
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.