← Back to home
Comparison · Infra & APIs

Currents vs werf

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

Currents vs werf: at a glance

FeatureCurrentswerf
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesplaywright, ci-observability, mcp, agent-accessdevops, kubernetes, ci-cd, helm
Last editorial update5d ago2h 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 werf?

werf v3.12.1 is tagged on every channel including stable and rock-solid, not just dev.

werf v3.12.1 fixes deploys that use saved plans containing a blind apply, and it is the first v3 release in the feed tagged on the alpha, beta, ea, stable and rock-solid channels rather than dev. The v2 line continues in parallel (v2.84.0 alpha) with the same build features.

Read the full werf trajectory →

Currents vs werf: 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.

W
werf
INFRA · APIS
5.0

werf v3.12.1 is tagged on every channel including stable and rock-solid, not just dev.

◆ Current state

werf v3.12.1 fixes deploys that use saved plans containing a blind apply, and it is the first v3 release in the feed tagged on the alpha, beta, ea, stable and rock-solid channels rather than dev. The v2 line continues in parallel (v2.84.0 alpha) with the same build features.

◆ Where it's heading

Through October the v3 line had shipped as dev releases that mirrored v2 features while adding its own Helm-compatible release storage. Putting v3.12.1 on all channels suggests v3 is now the main line and v2 is moving to maintenance, though the entry itself doesn't say so.

◆ Prediction

Expect v3 releases to keep landing on stable channels and v2 to receive fewer feature releases; a migration note for v2 users would confirm the shift.

Alternatives to Currents and werf

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 werf.

See all Currents alternatives → · See all werf alternatives →

Recent activity from Currents and werf

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

  1. 4d agowerfv3.12.1 reaches stable channels; saved-plan deploy fix
  2. 5d agowerfv2.84.0: publish cached images with require-built-images
  3. 5d agowerfv3.12.0: publish cached images with require-built-images
  4. 7d agoCurrents[Improved] A better GitHub run comment
  5. 7d agoCurrents[New] Project Overview
  6. 11d agowerfv2.83.0: pinned-commit submodule fetch, import recovery
  7. 11d agowerfv3.10.0: own Helm-compatible release storage, submodule fetch
  8. 12d agoCurrents[New] Trace API for agents ⚡
  9. 13d agowerfv2.82.0: git provenance for build commands, separate metadata repos
  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 werf?

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 werf?

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 werf?

Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.