OpenMQTTGateway
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
A side-by-side editorial comparison of Tekton Pipelines and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
Tekton names a new LTS while patching five older lines in the same fortnight
Tekton Pipeline maintains an unusually wide set of branches — v1.3, v1.6, v1.9, v1.12, v1.14 and now v1.15 all received releases recently, several cut within minutes of each other. v1.15.0 arrives as an LTS with configurable backoffs, following v1.14.0 which added pipelines-in-pipelines by reference along with leaner controllers and sturdier reconcilers. Every release carries a Rekor attestation UUID.
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.
Tekton Pipeline maintains an unusually wide set of branches — v1.3, v1.6, v1.9, v1.12, v1.14 and now v1.15 all received releases recently, several cut within minutes of each other. v1.15.0 arrives as an LTS with configurable backoffs, following v1.14.0 which added pipelines-in-pipelines by reference along with leaner controllers and sturdier reconcilers. Every release carries a Rekor attestation UUID.
Two things are consistent here: composability is the feature direction, and supply-chain provenance is non-negotiable — attestation is part of every release entry, including patches on years-old branches. The LTS designation matters more than the version number for platform teams, since it determines what they can standardise on without re-qualifying every quarter.
Expect patch releases to concentrate on v1.15 and the previous LTS lines, with older branches like v1.3 and v1.6 receiving fixes only until their support windows close.
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.
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 Tekton Pipelines or Dashy.
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
umbrelOS now pins any Docker container to the home screen — the app store stopped being the boundary.
ZoneMinder 1.38 finally split capturing from analysing — and added roles to a system that had none.
YARA ships bounds checks, not features — three patch releases published thirteen minutes apart.
Dokku ships patches weekly, and quietly grows a Kubernetes backend under its single-host roots.
Fail2Ban's last release was an interim beta 14 months ago; the feed spans eight years in six entries.
See all Tekton Pipelines alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tekton Pipelines and Dashy 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. Tekton Pipelines and Dashy 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 Tekton Pipelines alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tekton Pipelines alternatives" section above for the current picks, or visit /alternatives/tekton for the full list with editorial commentary on each.
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.