← Back to home
Comparison · Infra & APIs

Currents vs Dragonfly

A side-by-side editorial comparison of Currents and Dragonfly — release velocity, themes, recent moves, and the top alternatives to consider.

Currents vs Dragonfly: at a glance

FeatureCurrentsDragonfly
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesplaywright, ci-observability, mcp, agent-accessin-memory datastore, clustering, data consistency, performance
Last editorial update5d ago1h ago
WebsiteVisit →Visit →

What is Currents?

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.

Read the full Currents trajectory →

What is Dragonfly?

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.

Read the full Dragonfly trajectory →

Currents vs Dragonfly: editorial side-by-side

C
Currents
INFRA · APIS
6.3

Currents opens every project on a health verdict: trend, state, and what to fix first.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

D
Dragonfly
INFRA · APIS
5.0

Dragonfly fixes dropped writes during slot migration and rebalances slot-based sharding.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

The slot-based sharding flag looks likely to stay experimental for a while, with more balancing and migration fixes before it becomes a default.

Alternatives to Currents and Dragonfly

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.

See all Currents alternatives → · See all Dragonfly alternatives →

Recent activity from Currents and Dragonfly

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoDragonflyi1.40.13: Sidekiq queues placed on the same shard
  2. 5d agoDragonflyi2.0.5: Fibonacci hashing evens out slot-based sharding
  3. 5d agoDragonflyi1.40.12: single-shard BLMOVE completes in one hop
  4. 5d agoDragonflyi2.0.4: slot migration no longer drops writes to empty buckets
  5. 6d agoDragonflyi2.0.3: storage read-lifetime fix backported
  6. 6d agoDragonflyi1.40.11: storage read-lifetime fix backported
  7. 7d agoCurrents[Improved] A better GitHub run comment
  8. 7d agoCurrents[New] Project Overview
  9. 12d agoCurrents[New] Trace API for agents ⚡
  10. 19d agoCurrents[New] Run attachments
  11. 26d agoCurrents[New] Remote MCP Server with OAuth
  12. 1mo agoCurrents[New] Personal Access Tokens

Frequently asked questions

What is the difference between Currents and Dragonfly?

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.

Is Currents better than Dragonfly?

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.

What are the best alternatives to Currents?

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.

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.