Dashy
After the 4.5.0 drag-and-drop release, Dashy has settled into translations and dependency patches
Comparison · Infra & APIs
Quay vs werf
A side-by-side editorial comparison of Quay and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Quay vs werf: at a glance
What is Quay?
Quay ships nothing but CVE remediation, mirrored across two supported branches
Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.
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.
Quay vs werf: editorial side-by-side
Quay
5.0INFRA · APIS
Quay ships nothing but CVE remediation, mirrored across two supported branches
◆ Current state
Every entry in Quay's recent history is a security maintenance release, and they arrive as coordinated pairs — a 3.10.x and a 3.12.x tag cut hours apart carrying the same fixes cherry-picked to each branch. The content is dependency remediation against tracked advisories plus two SSRF hardening fixes, one in proxy cache upstream registry configuration and one in repository mirroring sources. No feature work appears in the window.
◆ Where it's heading
This is a registry in pure maintenance posture on its long-lived branches, with the release process itself automated down to changelog-bump commits. The recurring SSRF fixes across proxy cache and mirroring suggest a deliberate sweep through the code paths that fetch from upstream registries rather than isolated reports. Feature development, if it is happening, is landing on a branch this feed does not cover.
◆ Prediction
Expect the paired-branch cadence to continue at roughly the rate advisories land against the bundled Python and npm dependencies. The SSRF sweep looks close to complete, having now covered both proxy cache and mirroring.
werf
5.0INFRA · APIS
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.
Alternatives to Quay 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 Quay or werf.
Jackett
Jackett ships daily, and every release is tracker definitions chasing sites that moved
Unleash
Feature flags repositioned as the runtime kill switch for AI agents writing your code.
Kubernetes
The blog has become a teaching channel, with the real releases arriving as Gateway API and deprecation notices.
ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Recent activity from Quay and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13h agoQuayv3.12.21 patches six advisories and blocks SSRF in mirroring
- 15h agoQuayv3.10.25 carries the same advisory fixes to the 3.10 branch
- 21h agowerf2.77.1 fixes buildah imports on symlinked paths
- 21h agowerf3.x dev embeds deno and adds a registry-side cleanup report
- 1d agowerf2.76.0 adds condition-tracking gate and build timing
- 5d agowerflatest-signature
- 5d agowerf2.75.3 stops host cleanup wiping other versions' git cache
- 5d agowerf2.75.4 serializes base image pulls and fixes stapel scripts
- 20d agoQuayv3.12.20 bumps Go and blocks SSRF in proxy cache config
- 26d agoQuayv3.10.24 backports the Go bump and proxy cache SSRF fix
- 1mo agoQuayv3.10.23 clears PyJWT, urllib3 and shell-quote advisories
- 1mo agoQuayv3.12.19 clears the same four dependency advisories
Frequently asked questions
What is the difference between Quay and werf?
They serve adjacent needs but don't currently overlap on shipped themes. Quay and werf 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 Quay better than werf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Quay and werf 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 Quay?
Top Quay alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Quay alternatives" section above for the current picks, or visit /alternatives/quay 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.