← Back to home
Comparison · Infra & APIs

werf vs ZoneMinder

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

werf vs ZoneMinder: at a glance

FeaturewerfZoneMinder
SectorInfra & APIsInfra & APIs
Velocity score5.02.5
Sparks · 30d00
Top themesmulti-channel-releases, buildah, concurrency-fixes, kubernetes-deploysecurity-hardening, rbac, api-authorization, maintenance-branch
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is werf?

Four channels, one fix stream — werf's releases are mostly concurrency repairs.

werf publishes the same work across alpha, beta, ea, and stable channels plus a 3.x dev line, so a single fix surfaces three or four times under different version numbers. The substance in this window is almost entirely build-engine concurrency: parallel recovery failures, races in Dockerfile builds, concurrent stderr access, serialized base image pulls, retries when a cached image id goes missing. New function is thin — a case-insensitive-condition-tracking feature gate, a build time summary in debug mode, and a registry-side cleanup report.

Read the full werf trajectory →

What is ZoneMinder?

1.38.4 is a security release in all but name, closing ACL gaps across the API.

The 1.38 line is in maintenance, and 1.38.4 is almost entirely authorization work: per-monitor access control enforced on event, frame, zone, tag and media endpoints, two auth bypasses fixed in token validation, and SQL injection and overflow hardening. The 1.36 branch still receives backports, with 1.36.38 carrying its own SQL injection fix. The last feature release was 1.38.0 in February, which brought role-based access control, WebRTC and Go2RTC streaming, and the split of monitor function into separate capturing, analysing, and recording settings.

Read the full ZoneMinder trajectory →

werf vs ZoneMinder: editorial side-by-side

W
werf
INFRA · APIS
5.0

Four channels, one fix stream — werf's releases are mostly concurrency repairs.

◆ Current state

werf publishes the same work across alpha, beta, ea, and stable channels plus a 3.x dev line, so a single fix surfaces three or four times under different version numbers. The substance in this window is almost entirely build-engine concurrency: parallel recovery failures, races in Dockerfile builds, concurrent stderr access, serialized base image pulls, retries when a cached image id goes missing. New function is thin — a case-insensitive-condition-tracking feature gate, a build time summary in debug mode, and a registry-side cleanup report.

◆ Where it's heading

The 3.x dev line is accumulating what 2.x is stabilizing, and the one genuinely new thing in it is a deno binary embedded into werf releases behind a build tag. That is the only entry pointing anywhere beyond maintenance, and it is gated, so its intent is not yet stated. Otherwise the pattern is a mature build tool hardening buildah paths under parallelism, which is where self-hosted CI hits it hardest.

◆ Prediction

The embedded deno work is the thread to watch — if it stays behind its build tag it is an experiment, and if 3.x ships it on by default it implies a scripting surface for deployment.

Z
ZoneMinder
INFRA · APIS
2.5

1.38.4 is a security release in all but name, closing ACL gaps across the API.

◆ Current state

The 1.38 line is in maintenance, and 1.38.4 is almost entirely authorization work: per-monitor access control enforced on event, frame, zone, tag and media endpoints, two auth bypasses fixed in token validation, and SQL injection and overflow hardening. The 1.36 branch still receives backports, with 1.36.38 carrying its own SQL injection fix. The last feature release was 1.38.0 in February, which brought role-based access control, WebRTC and Go2RTC streaming, and the split of monitor function into separate capturing, analysing, and recording settings.

◆ Where it's heading

Every release since 1.38.0 has been consolidation of what that release opened up. RBAC shipped as a headline feature in February, and the four maintenance drops since have been finding the endpoints it did not cover — the familiar pattern when a permission model is retrofitted onto an API that predates it. Cadence is slow and irregular, months apart, with a 1.39 spec bump already visible in the repo but nothing from that series shipped.

◆ Prediction

Expect more per-endpoint ACL fixes on the 1.38 line before anything from 1.39 reaches release.

Alternatives to werf and ZoneMinder

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

See all werf alternatives → · See all ZoneMinder alternatives →

Recent activity from werf and ZoneMinder

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

  1. 13h agowerf2.77.1 fixes buildah imports on symlinked paths
  2. 13h agowerf3.x dev embeds deno and adds a registry-side cleanup report
  3. 20h agoZoneMinder1.38.4 closes API ACL gaps and two auth bypasses
  4. 1d agowerf2.76.0 adds condition-tracking gate and build timing
  5. 5d agowerflatest-signature
  6. 5d agowerf2.75.3 stops host cleanup wiping other versions' git cache
  7. 5d agowerf2.75.4 serializes base image pulls and fixes stapel scripts
  8. 2mo agoZoneMinder1.38.3 supersedes 1.38.2 with RBAC and injection fixes
  9. 2mo agoZoneMinderchore: bump redhat spec version to 1.39.11
  10. 5mo agoZoneMinder1.36.38 backports a SQL injection fix to the legacy branch
  11. 5mo agoZoneMinder1.38.1 unifies four ONVIF control modules into one
  12. 6mo agoZoneMinder1.38.0 adds RBAC, WebRTC streaming, and a monitor function split

Frequently asked questions

What is the difference between werf and ZoneMinder?

They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 werf better than ZoneMinder?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 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 ZoneMinder?

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