← Back to home
Comparison · Infra & APIs

Currents vs Woodpecker CI

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

Currents vs Woodpecker CI: at a glance

FeatureCurrentsWoodpecker CI
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d10
Top themesplaywright, ci-observability, mcp, agent-accessci-cd, pipeline, agent-security, forge-integration
Last editorial update2d ago4mo 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 Woodpecker CI?

Woodpecker CI hardens agent security and forge handling through its 3.14 release candidates

Woodpecker is iterating through 3.14.0 release candidates focused on security and agent/forge robustness: sanitizing agent-introduced state changes and log streaming, blocking registration as arbitrary agents, restricting log access, and cleaning up the Forge interface. Dependency security bumps (axios, otel, follow-redirects) and a lodash removal run throughout.

Read the full Woodpecker CI trajectory →

Currents vs Woodpecker CI: 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
Woodpecker CI
INFRA · APIS
0.0

Woodpecker CI hardens agent security and forge handling through its 3.14 release candidates

◆ Current state

Woodpecker is iterating through 3.14.0 release candidates focused on security and agent/forge robustness: sanitizing agent-introduced state changes and log streaming, blocking registration as arbitrary agents, restricting log access, and cleaning up the Forge interface. Dependency security bumps (axios, otel, follow-redirects) and a lodash removal run throughout.

◆ Where it's heading

The 3.14 line reads as a security-and-internals hardening cycle, tightening the agent trust boundary and forge integration rather than pushing features. The earlier 3.11 line shows the more typical mix of per-repo config features and fixes.

◆ Prediction

Expect 3.14.0 to converge to a stable release after the RC series, continuing the agent-security and forge-handling focus.

Alternatives to Currents and Woodpecker CI

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 Woodpecker CI.

See all Currents alternatives → · See all Woodpecker CI alternatives →

Recent activity from Currents and Woodpecker CI

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

  1. 4d agoCurrents[New] Project Overview
  2. 9d agoCurrents[New] Trace API for agents ⚡
  3. 16d agoCurrents[New] Run attachments
  4. 23d agoCurrents[New] Remote MCP Server with OAuth
  5. 29d agoCurrents[New] Personal Access Tokens
  6. 1mo agoCurrents[New] Shareable AI context for test failures ⚡
  7. 5mo agoWoodpecker CI3.14.0-rc.2: configurable agent reconnect, forge cleanup
  8. 6mo agoWoodpecker CI3.14.0-rc.1: security bumps, agent state sanitization
  9. 6mo agoWoodpecker CI3.14.0-rc.0: agent registration and log-access hardening
  10. 1y agoWoodpecker CI3.11.0-rc.0: per-repo config extension support

Frequently asked questions

What is the difference between Currents and Woodpecker CI?

They serve adjacent needs but don't currently overlap on shipped themes. Currents is currently shipping more aggressively (velocity 6.3 vs 0.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 Woodpecker CI?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Currents is currently shipping more aggressively (velocity 6.3 vs 0.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 Woodpecker CI?

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