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 Dokploy — 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.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
Dokploy cuts patch releases every one to two weeks, and the recent stream is dominated by hardening rather than features. v0.29.12 added AES-256-GCM encryption for environment variables at rest and made backups carry the full keyring; v0.29.13 closed an OS command injection in git clone across all providers. The newest tag says outright that it is bug fixes only. Alongside that, plan limits landed in v0.29.10.
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.
Dokploy cuts patch releases every one to two weeks, and the recent stream is dominated by hardening rather than features. v0.29.12 added AES-256-GCM encryption for environment variables at rest and made backups carry the full keyring; v0.29.13 closed an OS command injection in git clone across all providers. The newest tag says outright that it is bug fixes only. Alongside that, plan limits landed in v0.29.10.
The direction is a self-hosted platform trying to earn production trust: encrypted secrets, injection fixes, a pinned install script tied to each release, and Postgres query rewrites to stop hitting the 100-argument limit on rollbacks, schedules and backups. Plan limits point the other way — toward a commercial tier layered on the open-source core. Both arcs suggest the project is past feature-chasing and into making the platform defensible.
Expect the hardening thread to continue into the rest of the 0.29 line, with the plan-limits work being the seed of a paid tier that gets more definition before a 0.30 release.
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 Dokploy.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
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.
See all Dashy alternatives → · See all Dokploy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy and Dokploy are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dashy and Dokploy are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Dokploy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokploy alternatives" section above for the current picks, or visit /alternatives/dokploy for the full list with editorial commentary on each.