Nautobot
Nautobot 3.3 alpha adds API rate limits while 3.2.9 stops cross-user token reads.
A side-by-side editorial comparison of OpenMQTTGateway and Quay — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMQTTGateway returns after 22 months with a security-first 1.9.0.
OpenMQTTGateway shipped v1.9.0 on November 7, its first release since January 2025. It moves to the Arduino ESP32 core 3.x, ships Theengs Decoder 2.5.0 with a fix for a BLE advertisement parsing flaw affecting every earlier release, and hardens buffer handling across MQTT, HTTP, BLE and RF input. Upgrade notes warn that some Home Assistant unique_ids change and that encrypted BLE devices are skipped until a key is set.
Quay keeps both enterprise branches on a monthly CVE-patch metronome — and nothing else.
All ten releases in this window are security maintenance: dependency bumps for CVEs, SSRF hardening in mirroring and proxy cache, and a robot-token visibility fix for readonly superusers. The October pair (3.12.23 and 3.10.27) patches the same four CVEs — immutable, qs, lxml, WebOb — plus a compression bump. Neither line has shipped a user-facing feature in four months.
OpenMQTTGateway shipped v1.9.0 on November 7, its first release since January 2025. It moves to the Arduino ESP32 core 3.x, ships Theengs Decoder 2.5.0 with a fix for a BLE advertisement parsing flaw affecting every earlier release, and hardens buffer handling across MQTT, HTTP, BLE and RF input. Upgrade notes warn that some Home Assistant unique_ids change and that encrypted BLE devices are skipped until a key is set.
Earlier releases made the gateway independent of controllers and external brokers. The return release is about safety and a modern ESP32 base rather than new features, which suggests the project is resetting its foundation before resuming feature work.
Expect the promised security advisory for the Theengs Decoder flaw and 1.9.x fixes for the Home Assistant entity changes; whether regular cadence resumes is not yet clear from the entries.
All ten releases in this window are security maintenance: dependency bumps for CVEs, SSRF hardening in mirroring and proxy cache, and a robot-token visibility fix for readonly superusers. The October pair (3.12.23 and 3.10.27) patches the same four CVEs — immutable, qs, lxml, WebOb — plus a compression bump. Neither line has shipped a user-facing feature in four months.
The 3.10 and 3.12 lines move in lockstep, typically within hours to days of each other, on a roughly monthly cadence. New Containerfile.art files for ART/Konflux builds point to packaging work on Red Hat's build pipeline rather than product changes. Feature work, if any, is not surfacing in these maintenance branches.
Expect the next 3.12.x/3.10.x pair in roughly a month with another batch of CVE bumps. The entries give no signal of when or whether new capabilities will land on these lines.
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 Quay.
Nautobot 3.3 alpha adds API rate limits while 3.2.9 stops cross-user token reads.
SpinupWP now writes DNS records for you, starting with Cloudflare and Route 53.
One Node.js Brotli bug and a compromised CA bundle force ten patches across the Elastic Stack.
Parse Server 9.11.1 alphas close two beforeSave advisories, one a server crash.
GitLab sells Orbit as the evidence layer for agent pilots and AI-code rules.
Kestra's feed is design-system package releases while 2.1.0 waits past its first RC.
See all OpenMQTTGateway alternatives → · See all Quay alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Quay is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Quay is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Quay alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Quay alternatives" section above for the current picks, or visit /alternatives/quay for the full list with editorial commentary on each.