Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of Dashy and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Dashy ships a release per merged PR — the real 4.5 features are already scrolling off the feed.
The self-hosted dashboard cuts a version for essentially every merged pull request, so the recent window is a mix of dependabot bumps, German translations, an out-of-memory fix from unclosed secureConnect listeners, OIDC post-logout redirect support, and new sorting by provider and item ID. The 4.5.0 release that carries the substance — drag-and-drop editing of sections, items and widgets, a rebuilt GitHub stats widget on the official API, and number formatting in the custom-api widget — sits just outside this window.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
werf publishes into parallel channels simultaneously — v2.75.3 tagged beta, ea and stable landed the same minute as v2.75.4 for alpha, while the v3 line runs separately through 3.0.2, a 3.0.0 alpha and a 3.1.0 dev build. The 2.x entries are corrective: buildah pull retries and serialisation, a stapel service script made executable regardless of umask, host cleanup no longer wiping other werf versions' git cache. The v3 entries carry the actual features.
The self-hosted dashboard cuts a version for essentially every merged pull request, so the recent window is a mix of dependabot bumps, German translations, an out-of-memory fix from unclosed secureConnect listeners, OIDC post-logout redirect support, and new sorting by provider and item ID. The 4.5.0 release that carries the substance — drag-and-drop editing of sections, items and widgets, a rebuilt GitHub stats widget on the official API, and number formatting in the custom-api widget — sits just outside this window.
Development is steady and community-driven, with a maintainer handling auth and stability while contributors add widgets, sorting and translations. The direction after 4.5.0 is refinement rather than expansion: fix what the new editing surface exposed, round out OIDC, keep dependencies current. The per-PR release cadence makes the feed noisy relative to how much actually changes.
Expect the 4.5.x patch stream to continue at roughly a release every few days, dominated by dependency bumps and follow-up fixes to the drag-and-drop editor. Larger features will land in a 4.6 cut rather than trickling through patches.
werf publishes into parallel channels simultaneously — v2.75.3 tagged beta, ea and stable landed the same minute as v2.75.4 for alpha, while the v3 line runs separately through 3.0.2, a 3.0.0 alpha and a 3.1.0 dev build. The 2.x entries are corrective: buildah pull retries and serialisation, a stapel service script made executable regardless of umask, host cleanup no longer wiping other werf versions' git cache. The v3 entries carry the actual features.
The v3 work is about making builds predictable and inspectable: embedded kubeconform schemas, a per-project meta-repo safeguard with a migration path, additional patches files with the defaults disableable, and repo-built scratch images made readable by dive. Meanwhile v3 alphas are restoring flags that v3 had dropped, which suggests the major is being trimmed and then walked back based on review. Dockerfile fidelity — COPY --parents, COPY/ADD --exclude in staged builds — is a recurring thread across both lines.
Expect the 2.75 line to keep taking build-backend fixes while v3 stabilises, with more v2 flags restored in v3 alphas as review findings land before the major reaches a stable channel.
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 Dashy or werf.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy is currently shipping more aggressively (velocity 6.3 vs 5.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dashy is currently shipping more aggressively (velocity 6.3 vs 5.0), 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.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.
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.