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 KubeArmor and OpenMQTTGateway — release velocity, themes, recent moves, and the top alternatives to consider.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
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.
KubeArmor's feed shows five release-candidate tags and one merge-commit entry from October for 1.7.6 and 1.7.7, each carrying one or two commits: a relay-channel memory leak fix with pprof added, a snitch fix, removed limits and an AppArmor alert-throttling fix. GitHub shows 1.7.6 went final on 23 October, which the feed missed; it replaced the execve kprobe with a tracepoint, fixed pods not terminating on AppArmor nodes, added audit alerts from the BPF-LSM enforcer and expanded arm64 eBPF testing.
The project is mid-way through stabilising its eBPF enforcement across architectures: arm64 syscall matching, multi-arch image tests and the move from kprobes to tracepoints all reduce kernel-specific breakage. The release process remains RC-heavy, with near-identical tags cut minutes apart, which makes the feed a poor guide to what users actually get.
Expect 1.7.7 final soon after rc1, carrying the AppArmor throttling fix. The arm64 work in 1.7.6 suggests further multi-architecture fixes rather than new policy features next.
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.
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 KubeArmor or OpenMQTTGateway.
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 KubeArmor alternatives → · See all OpenMQTTGateway alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. KubeArmor 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. KubeArmor 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 KubeArmor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "KubeArmor alternatives" section above for the current picks, or visit /alternatives/kubearmor for the full list with editorial commentary on each.
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.