DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of Dashy and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Dashy | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | internationalization, self-hosted, dashboard, patch-cadence | notifications, developer-infrastructure, rbac, workflow-automation |
| Last editorial update | 3d ago | 12h ago |
| Website | Visit → | — |
A release per merged PR, and right now nearly every one is a translation string.
Dashy cuts a version tag for each merged pull request, so the changelog reads at commit granularity. The current run is almost entirely localisation and dependency work — Traditional Chinese completed, hard-coded strings extracted, German added for the edit-item dialog — broken only by a mobile search fix and two grouped dependency bumps.
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
Dashy cuts a version tag for each merged pull request, so the changelog reads at commit granularity. The current run is almost entirely localisation and dependency work — Traditional Chinese completed, hard-coded strings extracted, German added for the edit-item dialog — broken only by a mobile search fix and two grouped dependency bumps.
The project is in maintenance rhythm: no feature work in this window, and the one substantive thread is making the UI translatable by pulling hard-coded strings out so contributors can localise them. That extraction is what enabled the German and Chinese contributions that follow it, which is the only causal chain visible in the feed.
Expect more single-PR patch tags in the same mix — further language contributions now that strings are extracted, plus dependabot groups. Nothing in these entries points to a feature release.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.
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 Dashy or Knock.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy and Knock are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dashy and Knock are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.
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.