← Back to home
Comparison · Infra & APIs

Kubeshark vs OpenMQTTGateway

A side-by-side editorial comparison of Kubeshark and OpenMQTTGateway — release velocity, themes, recent moves, and the top alternatives to consider.

Kubeshark vs OpenMQTTGateway: at a glance

FeatureKubesharkOpenMQTTGateway
SectorInfra & APIsInfra & APIs
Velocity score0.02.5
Sparks · 30d00
Top themeskubernetes, network-observability, packet-capture, ebpfiot gateway, bluetooth le, mqtt, home automation
Last editorial update3mo ago3h ago
WebsiteVisit →Visit →

What is Kubeshark?

Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.

Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.

Read the full Kubeshark trajectory →

What is OpenMQTTGateway?

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.

Read the full OpenMQTTGateway trajectory →

Kubeshark vs OpenMQTTGateway: editorial side-by-side

K
Kubeshark
INFRA · APIS
0.0

Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.

◆ Current state

Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.

◆ Where it's heading

The product is moving down the stack. It started as an API-level traffic viewer and the recent work is all about L4 — connectivity maps, raw PCAP export, mapping L7 calls onto the connections beneath them — which puts it closer to a cluster-wide packet capture tool than a service-mesh observability dashboard. The licensing is moving in the opposite direction of the feature set: an almost-unlimited complimentary licence through the end of 2025 was replaced by one capped at 100 nodes, so the free tier is being defined rather than left open. Two releases also mention agentic infrastructure being staged but not yet usable.

◆ Prediction

Expect V2 to consolidate onto the new backend and the legacy V1 path to be dropped once the transition completes, since the release notes already describe V1 as being sunset. The staged agentic infrastructure is the most likely candidate for the next substantive feature, given it has been shipped inert twice.

O
OpenMQTTGateway
INFRA · APIS
2.5

OpenMQTTGateway returns after 22 months with a security-first 1.9.0.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to Kubeshark and OpenMQTTGateway

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 Kubeshark or OpenMQTTGateway.

See all Kubeshark alternatives → · See all OpenMQTTGateway alternatives →

Recent activity from Kubeshark and OpenMQTTGateway

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoOpenMQTTGatewayOpenMQTTGateway v1.9.0
  2. 9mo agoKubesharkv52.12.0 moves every service domain to kubeshark.com
  3. 9mo agoKubesharkComplimentary licence is redefined as free up to 100 nodes
  4. 10mo agoKubesharkBackend fully rewritten for V2, with L7-to-L4 traffic mapping ⚡
  5. 11mo agoKubesharkNear-unlimited complimentary licence bundled into the Helm chart
  6. 1y agoOpenMQTTGatewayAdaptive scanning restart bug fixed
  7. 1y agoOpenMQTTGatewayAn MQTT broker moves inside the gateway ⚡
  8. 2y agoOpenMQTTGatewayTheengs Bridge hardware and Ethernet onboarding
  9. 3y agoOpenMQTTGatewayWeb interface removes the controller dependency
  10. 3y agoOpenMQTTGatewayWorkaround for stuck BLE scans

Frequently asked questions

What is the difference between Kubeshark and OpenMQTTGateway?

They serve adjacent needs but don't currently overlap on shipped themes. OpenMQTTGateway is currently shipping more aggressively (velocity 2.5 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 Kubeshark better than OpenMQTTGateway?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenMQTTGateway is currently shipping more aggressively (velocity 2.5 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 Kubeshark?

Top Kubeshark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kubeshark alternatives" section above for the current picks, or visit /alternatives/kubeshark for the full list with editorial commentary on each.

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.