werf
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
A side-by-side editorial comparison of OpenMQTTGateway and Rancher — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
The last release was January 2025, a single bug fix for adaptive scanning restarting the gateway. Before that, the project moved steadily toward standing alone: 1.8.0 embedded an MQTT broker via PicoMQTT so a gateway no longer needs an external server, 1.6.0 added a web interface so it no longer needs a home automation controller to configure, and 1.5.0 brought device trackers for presence detection with over-the-air updates from the controller. Hardware arrived alongside software, with the Theengs Bridge in 1.7.0 and the Theengs Plug in 1.3.0.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Rancher's public release feed is a tag stream rather than a changelog. The two maintenance releases here — 2.12.12 and 2.11.16, tagged seconds apart — each carry a single line pointing readers to the Prime documentation for the actual notes. The 2.15 line appears only as build metadata: an rc5 image and component manifest, then an alpha tag whose entire content is switching the dashboard to its release build.
The last release was January 2025, a single bug fix for adaptive scanning restarting the gateway. Before that, the project moved steadily toward standing alone: 1.8.0 embedded an MQTT broker via PicoMQTT so a gateway no longer needs an external server, 1.6.0 added a web interface so it no longer needs a home automation controller to configure, and 1.5.0 brought device trackers for presence detection with over-the-air updates from the controller. Hardware arrived alongside software, with the Theengs Bridge in 1.7.0 and the Theengs Plug in 1.3.0.
The arc through 1.2 to 1.8 is one of progressive independence — first from a controller for configuration, then from a broker for messaging — turning a bridge component into a self-contained device. Release intervals widened throughout: monthly in early 2023, then annual, then nothing for nineteen months. Whatever the roadmap was, the feed has not recorded activity since.
The evidence here does not support a confident prediction about what ships next; the project has published nothing in nineteen months. If it resumes, the unfinished thread is the embedded broker, which shipped in 1.8.0 and received only a scanning bug fix afterward.
Rancher's public release feed is a tag stream rather than a changelog. The two maintenance releases here — 2.12.12 and 2.11.16, tagged seconds apart — each carry a single line pointing readers to the Prime documentation for the actual notes. The 2.15 line appears only as build metadata: an rc5 image and component manifest, then an alpha tag whose entire content is switching the dashboard to its release build.
Three branches are live at once, with maintenance flowing to 2.11 and 2.12 while 2.15 works through release candidates. Because notes for the supported branches are published behind the Prime docs, this feed will keep showing cadence without content, and the only readable signals are structural: which branches get tagged, and how far the 2.15 candidates have progressed.
The 2.15 line looks close to shipping — rc5 followed by an alpha tag pinning the dashboard to a release build — so the next visible move is a 2.15.0 general release tag, again with its notes pointing to Prime documentation rather than appearing here.
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 OpenMQTTGateway or Rancher.
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.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all OpenMQTTGateway alternatives → · See all Rancher alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rancher is currently shipping more aggressively (velocity 5.0 vs 0.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. Rancher is currently shipping more aggressively (velocity 5.0 vs 0.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 OpenMQTTGateway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenMQTTGateway alternatives" section above for the current picks, or visit /alternatives/openmqttgateway for the full list with editorial commentary on each.
Top Rancher alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rancher alternatives" section above for the current picks, or visit /alternatives/rancher for the full list with editorial commentary on each.