ESPHome
ESPHome 2026.10.0 lands after six betas of audio, memory and ESP-IDF 6.1 work.
A side-by-side editorial comparison of Currents and Dragonfly — release velocity, themes, recent moves, and the top alternatives to consider.
Currents opens every project on a health verdict: trend, state, and what to fix first.
Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API built for agents. The Oct 19 Project Overview adds a human-facing counterpart: projects now open on a page saying whether the suite is healthy, which way it is trending, and what to fix first.
Dragonfly fixes dropped writes during slot migration and rebalances slot-based sharding.
Dragonfly is maintaining two incremental lines, 1.40 and 2.0, with small, targeted releases. The 2.0 line fixed a slot-migration bug that silently dropped journal writes into empty buckets and changed experimental slot-based sharding to Fibonacci hashing so keys spread evenly. The 1.40 line received BLMOVE and Sidekiq queue-placement optimizations.
Currents is a Playwright test dashboard rebuilding itself around agent access. Since September it shipped agent-readable failure links, scoped personal access tokens, a hosted MCP server with OAuth, run attachments and a trace API built for agents. The Oct 19 Project Overview adds a human-facing counterpart: projects now open on a page saying whether the suite is healthy, which way it is trending, and what to fix first.
The product is converging on triage as its core job, for both audiences. Agents get granular paths into failures, traces and logs; humans get a prioritized summary instead of raw run lists. Both point at the same promise: Currents decides what to look at, not just stores results.
Likely next is linking Overview's fix-first items to the agent surfaces, so a prioritized problem can be handed straight to an MCP or trace-API session. The entries don't yet show that connection.
Dragonfly is maintaining two incremental lines, 1.40 and 2.0, with small, targeted releases. The 2.0 line fixed a slot-migration bug that silently dropped journal writes into empty buckets and changed experimental slot-based sharding to Fibonacci hashing so keys spread evenly. The 1.40 line received BLMOVE and Sidekiq queue-placement optimizations.
Most of the work is in cluster mode: migrations, slot placement and topology replies. That suggests the 2.x line is being hardened for multi-node deployments, while 1.40 still gets backports and small performance fixes.
The slot-based sharding flag looks likely to stay experimental for a while, with more balancing and migration fixes before it becomes a default.
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 Currents or Dragonfly.
ESPHome 2026.10.0 lands after six betas of audio, memory and ESP-IDF 6.1 work.
Cronicle keeps patching vulnerable dependencies, two more bumps in three days.
Retool's week is security disclosures and patch trains after a fast run of model launches.
Knock adds single-step test runs and retries for failed workflow runs.
Sonarr 5.0 builds add Trakt Smart Lists, OIDC Remember Me and more accessibility fixes.
Redocly keeps Reunite project sign-ins alive for 30 days and hardens Visual review login.
See all Currents alternatives → · See all Dragonfly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Currents 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. Currents 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 Currents alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Currents alternatives" section above for the current picks, or visit /alternatives/currents-dev for the full list with editorial commentary on each.
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.