Apache CloudStack
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Comparison · Infra & APIs
OpenMQTTGateway vs Skipper
A side-by-side editorial comparison of OpenMQTTGateway and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMQTTGateway vs Skipper: at a glance
What is OpenMQTTGateway?
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.
What is Skipper?
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
OpenMQTTGateway vs Skipper: editorial side-by-side
OpenMQTTGateway
0.0INFRA · APIS
OpenMQTTGateway spent three years shedding its dependencies, then stopped shipping entirely.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Skipper
5.0INFRA · APIS
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
◆ Current state
Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.
◆ Where it's heading
Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.
◆ Prediction
Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.
Alternatives to OpenMQTTGateway and Skipper
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 Skipper.
Kinsta
Kinsta is moving MyKinsta's controls into its API, one surface per month
Verdaccio
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
ToolJet
Observability lands on OpenTelemetry semconv in the LTS train
Honeycomb
Canvas agents gain memory, and onboarding moves into the editor
GitHub
Security and governance controls catch up to the Copilot build-out
See all OpenMQTTGateway alternatives → · See all Skipper alternatives →
Recent activity from OpenMQTTGateway and Skipper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15h agoSkipperMove OIDC flow protection from Referer to cookies
- 15h agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
- 1d agoSkipperEskip predicates and filters accept negative numbers
- 1d agoSkipperFix token introspection handling
- 1d agoSkipperFix grant auth flow
- 1d agoSkipperUpdate outdated golang.org/x dependencies
- 1y agoOpenMQTTGatewayAdaptive scanning restart bug fixed
- 1y agoOpenMQTTGatewayAn MQTT broker moves inside the gateway ⚡
- 2y agoOpenMQTTGatewayTheengs Bridge hardware and Ethernet onboarding
- 3y agoOpenMQTTGatewayWeb interface removes the controller dependency
- 3y agoOpenMQTTGatewayWorkaround for stuck BLE scans
- 3y agoOpenMQTTGatewayPresence detection via automatic device trackers
Frequently asked questions
What is the difference between OpenMQTTGateway and Skipper?
They serve adjacent needs but don't currently overlap on shipped themes. Skipper 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.
Is OpenMQTTGateway better than Skipper?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper 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.
What are the best alternatives to OpenMQTTGateway?
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.
What are the best alternatives to Skipper?
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.