cli
cli refines terminal output one formatting detail at a time.
Comparison · Infra & APIs
Dragonfly vs Knock
A side-by-side editorial comparison of Dragonfly and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly vs Knock: at a glance
| Feature | Dragonfly | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | correctness, redis-compatibility, cluster, upstream-sync | notification infrastructure, data sources, agent interface, workflow primitives |
| Last editorial update | 6h ago | 5h ago |
| Website | Visit → | — |
What is Dragonfly?
Dragonfly is spending its releases on correctness debt, not features.
The last two months are almost entirely correctness work: a pub/sub ordering bug that silently discarded queued messages on unsubscribe, a multi-key PFCOUNT that read sixteen wrong registers, an uninitialized pointer in the sparse HyperLogLog promote path, and now cluster FLUSHSLOTS that was not journaled inside its own flush transaction. The one structural move is the resync of the forked hyperloglog.c against valkey upstream, which cut divergence from 2,139 lines to 767 and pulled in a CVE fix plus AVX2 and NEON merge kernels. New user-facing options are rare; the list compression tuning flags are the exception.
What is Knock?
Knock is pulling every customer-data source into notifications, then putting an agent on top.
Knock is a notification infrastructure layer, and the last two months have gone into two things: widening what can trigger a workflow, and making the resulting data legible. Amplitude and Clay both landed as first-class data sources, so product events, cohort changes and enriched CRM rows now drive messaging directly rather than through customer-written glue. The workflow engine gained a wait-for-event primitive, and the template editor was rebuilt around block editing.
Dragonfly vs Knock: editorial side-by-side
Dragonfly
5.0INFRA · APIS
Dragonfly is spending its releases on correctness debt, not features.
◆ Current state
The last two months are almost entirely correctness work: a pub/sub ordering bug that silently discarded queued messages on unsubscribe, a multi-key PFCOUNT that read sixteen wrong registers, an uninitialized pointer in the sparse HyperLogLog promote path, and now cluster FLUSHSLOTS that was not journaled inside its own flush transaction. The one structural move is the resync of the forked hyperloglog.c against valkey upstream, which cut divergence from 2,139 lines to 767 and pulled in a CVE fix plus AVX2 and NEON merge kernels. New user-facing options are rare; the list compression tuning flags are the exception.
◆ Where it's heading
Two threads run in parallel. One reduces the cost of carrying a Redis fork by re-syncing individual files against valkey and leaving provenance notes so the next sync is cheap. The other hardens the V2 IO loop while the V1 path still takes the fixes — several commits explicitly defer the V2 half of a fix to a later change, so the two loops are not at parity. Cluster correctness around slot migration and journaling is the newest front.
◆ Prediction
The deferred V2 IO-loop fixes are the obvious next commits, and more forked Redis files are likely to get the same upstream resync treatment now that the pattern and its accounting are established.
Knock
6.3INFRA · APIS
Knock is pulling every customer-data source into notifications, then putting an agent on top.
◆ Current state
Knock is a notification infrastructure layer, and the last two months have gone into two things: widening what can trigger a workflow, and making the resulting data legible. Amplitude and Clay both landed as first-class data sources, so product events, cohort changes and enriched CRM rows now drive messaging directly rather than through customer-written glue. The workflow engine gained a wait-for-event primitive, and the template editor was rebuilt around block editing.
◆ Where it's heading
The shape is a product moving up from delivery mechanics toward the surrounding workflow. Sources reduce the integration code a customer writes before Knock is useful; the agent layer reduces the reporting work after. Category and tag management being pulled into dedicated dashboard pages is the housekeeping that follows: the primitives got numerous enough to need their own administration surface.
◆ Prediction
Expect the data-source list to keep growing along the same lines — warehouse and product-analytics tools that already hold the user state Knock needs — and for the agent to be given more of the dashboard's read surface.
Alternatives to Dragonfly 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 Dragonfly or Knock.
roxygen2
roxygen2 8.0 cut stringi out of the entire devtools dependency tree.
pak
pak's roadmap is written by enterprise R deployments and Posit Package Manager.
renv
renv 1.2 made installs parallel, its biggest performance change in years.
pkgload
pkgload is quietly wiring R package development into modern IDE tooling.
bench
bench has settled into slow, careful upkeep of R's benchmarking workhorse.
See all Dragonfly alternatives → · See all Knock alternatives →
Recent activity from Dragonfly and Knock
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoDragonflyBackported memory-accounting fix; FLUSHSLOTS journaled in-transaction
- 1d agoKnockCategory + tag management
- 7d agoKnockAmplitude data source
- 14d agoDragonflyi1.39.11: chore(hll): sync hyperloglog.c with valkey upstream (#7961)
- 14d agoKnockAnalytics in the Knock agent ⚡
- 15d agoKnockWait for event function
- 16d agoKnockClay data source
- 20d agoDragonflyFix mutable cross-thread access on shared reply builder
- 21d agoKnockRedesigned template editor
- 22d agoDragonflyi1.39.9: fix(facade): preserve pub/sub order on unsubscribe (v1 IO loop) (#7909)
- 1mo agoDragonflyi1.39.6: test: skip V2-only pause tests under V1 (#7822)
- 1mo agoDragonflyi1.39.4: Add list compression tuning flags (#7762)
Frequently asked questions
What is the difference between Dragonfly 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 Dragonfly 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 Dragonfly?
Top Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly 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.