← Back to home
Comparison · Infra & APIs

Depot vs Woodpecker CI

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

Depot vs Woodpecker CI: at a glance

FeatureDepotWoodpecker CI
SectorInfra & APIsInfra & APIs
Velocity score10.00.0
Sparks · 30d20
Top themesdepot-ci, api-and-cli, test-analytics, agent-opsci-cd, pipeline, agent-security, forge-integration
Last editorial update3d ago5h ago
WebsiteVisit →

What is Depot?

Depot pushes its CI product toward agent control and test intelligence as it nears platform maturity.

Depot accelerates container builds and CI, and the recent stretch is almost entirely about maturing Depot CI from runner into platform. In a single window it shipped a GA API and CLI, a test-results product with cross-provider analytics, plus workflow browsing, usage tracking, nested virtualization, and AI failure diagnosis via Sherlock.

Read the full Depot 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 →

Depot vs Woodpecker CI: editorial side-by-side

D
Depot
INFRA · APIS
10.0

Depot pushes its CI product toward agent control and test intelligence as it nears platform maturity.

◆ Current state

Depot accelerates container builds and CI, and the recent stretch is almost entirely about maturing Depot CI from runner into platform. In a single window it shipped a GA API and CLI, a test-results product with cross-provider analytics, plus workflow browsing, usage tracking, nested virtualization, and AI failure diagnosis via Sherlock.

◆ Where it's heading

Depot is making Depot CI both programmable and observable: the GA API and CLI expose every dashboard action to scripts and agents, while test results and Sherlock add the diagnostic layer on top. Notably, the test analytics reach into GitHub Actions too — a wedge to pull Actions users onto Depot without forcing a full migration first.

◆ Prediction

Expect the API surface and test analytics to deepen together — agent-driven retries informed by flaky-test detection — as Depot positions CI as something agents operate, not just humans.

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

See all Depot alternatives → · See all Woodpecker CI alternatives →

Recent activity from Depot and Woodpecker CI

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

  1. 4d agoDepotDepot CI API and CLI are now generally available
  2. 6d agoDepotTest results for your CI jobs are now available in beta
  3. 7d agoDepotDepot CI usage now on the org usage page
  4. 7d agoDepotExplore Depot CI activity by repository and workflow
  5. 7d agoDepotDepot CI now supports link-local IPv6
  6. 10d agoDepotView or copy docs pages as markdown
  7. 1mo agoWoodpecker CI3.14.0-rc.2: configurable agent reconnect, forge cleanup
  8. 1mo agoWoodpecker CI3.14.0-rc.1: security bumps, agent state sanitization
  9. 2mo agoWoodpecker CI3.14.0-rc.0: agent registration and log-access hardening
  10. 8mo agoWoodpecker CI3.11.0-rc.0: per-repo config extension support

Frequently asked questions

What is the difference between Depot and Woodpecker CI?

They serve adjacent needs but don't currently overlap on shipped themes. Depot is currently shipping more aggressively (velocity 10.0 vs 0.0), with 2 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 Depot better than Woodpecker CI?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 10.0 vs 0.0), with 2 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 Depot?

Top Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot 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.