← Back to home
Comparison · Infra & APIs

werf vs Wazuh

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

werf vs Wazuh: at a glance

FeaturewerfWazuh
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themesdevops, kubernetes, helm, typescript chartssiem, endpoint-security, open-source, security-hardening
Last editorial update1d ago7h ago
WebsiteVisit →Visit →

What is werf?

werf 3.13 renders TypeScript charts with Node.js and drops the feature flag.

werf released v3.13.0 and v2.85.0 on the alpha channel on November 12. v3.13.0 renders TypeScript Helm charts with Node.js instead of Deno and no longer needs NELM_FEAT_TYPESCRIPT, deploys published bundles the same way as converge and fixes subchart values. v2.85.0 refuses charts that require werf v3 and stops failed Buildah builds leaking containers.

Read the full werf trajectory →

What is Wazuh?

Wazuh hardens its 4.14 line while 5.0 rebuilds how agents talk to the manager.

Wazuh ships 4.14 patch releases roughly every two to three weeks, and almost all of the content is security hardening: path traversal and command injection fixes, input validation in the cluster code, connection deadlines and memory leak fixes. 4.14.10 also added memory limits for oversized rulesets and queue warnings for the vulnerability scanner. In parallel, 5.0.0 reached its second release candidate on October 30.

Read the full Wazuh trajectory →

werf vs Wazuh: editorial side-by-side

W
werf
INFRA · APIS
5.0

werf 3.13 renders TypeScript charts with Node.js and drops the feature flag.

◆ Current state

werf released v3.13.0 and v2.85.0 on the alpha channel on November 12. v3.13.0 renders TypeScript Helm charts with Node.js instead of Deno and no longer needs NELM_FEAT_TYPESCRIPT, deploys published bundles the same way as converge and fixes subchart values. v2.85.0 refuses charts that require werf v3 and stops failed Buildah builds leaking containers.

◆ Where it's heading

werf keeps v2 and v3 moving together through its release channels, but v3 gets the new deploy features while v2 now guards against v3-only charts. TypeScript charts moving out from behind a flag shows v3's Helm-alternative work maturing.

◆ Prediction

Expect v3.13.x to move up to beta and stable over the next weeks, and further v2 releases limited to fixes and v3 compatibility guards.

W
Wazuh
INFRA · APIS
5.0

Wazuh hardens its 4.14 line while 5.0 rebuilds how agents talk to the manager.

◆ Current state

Wazuh ships 4.14 patch releases roughly every two to three weeks, and almost all of the content is security hardening: path traversal and command injection fixes, input validation in the cluster code, connection deadlines and memory leak fixes. 4.14.10 also added memory limits for oversized rulesets and queue warnings for the vulnerability scanner. In parallel, 5.0.0 reached its second release candidate on October 30.

◆ Where it's heading

5.0 is the real change: agents move to HTTPS for talking to the manager, a new detection engine replaces the 4.x analysis daemon, and every server install becomes a cluster node. The 4.14 branch, meanwhile, reads like a security audit being worked through release by release, which keeps current installs safe while 5.0 settles.

◆ Prediction

More 5.0 release candidates are likely before a final release, and 4.14 patch releases with security fixes should keep coming every few weeks; a 5.0 GA date is not stated in these entries.

Alternatives to werf and Wazuh

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

See all werf alternatives → · See all Wazuh alternatives →

Recent activity from werf and Wazuh

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

  1. 1d agowerfwerf v2.85.0 refuses v3-only charts, fixes leaked build containers
  2. 1d agowerfwerf v3.13.0: TypeScript charts on Node.js, no feature flag
  3. 2d agoWazuhWazuh 4.14.11 RC1 tightens group paths and agent enrollment
  4. 5d agoWazuhWazuh 4.14.10 adds ruleset memory limits and closes a root injection
  5. 14d agoWazuhWazuh 5.0 RC2 swaps in a new detection engine
  6. 15d agowerfv2.84.1: Docker Hub login, uninstall hang and upload retry fixes
  7. 15d agowerfv3.12.2: --values can override secrets, RUN mount rebuild fixes
  8. 23d agowerfv3.12.1 reaches stable channels; saved-plan deploy fix
  9. 24d agowerfv2.84.0: publish cached images with require-built-images
  10. 29d agoWazuhWazuh 4.14.9 adds compiler hardening to Linux binaries
  11. 1mo agoWazuhWazuh 5.0 RC1 moves agents to HTTPS and makes every server a cluster
  12. 1mo agoWazuhWazuh 4.14.8 fixes an alert-stopping deadlock

Frequently asked questions

What is the difference between werf and Wazuh?

They serve adjacent needs but don't currently overlap on shipped themes. werf and Wazuh are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is werf better than Wazuh?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf and Wazuh are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

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.

What are the best alternatives to Wazuh?

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