Ross ROSS = Recommend OSS · open-source software intelligence for agents

eclipse-zenoh/zenoh

zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks. observed · 2026-08-28

github.com/eclipse-zenoh/zenoh · homepage · Rust · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

99/100

  • Activity 99
  • Release rhythm 98
  • Longevity 100

Flags: no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 14.0
  • age_days: 2416
  • days_rel: 19
  • days_push: 8
  • n_releases_24m: 25

Full methodology

Adoption not part of the score

3126 stars · 353 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Zenoh is a Rust-implemented pub/sub/query protocol and library that unifies data in motion, data at rest, and computations with minimal wire overhead (5 bytes). It includes a router daemon (zenohd), multi-language bindings, and support for geo-distributed storages, queries, and queryables from cloud to microcontroller.

Use cases

  • publish sensor data from embedded devices to the cloud
  • build a distributed pub/sub system for robotics
  • query geo-distributed data stores transparently
  • communicate between ROS 2 nodes over the network
  • stream telemetry with minimal bandwidth overhead
  • implement RPC between microservices and edge devices
  • bridge enterprise and embedded systems with one protocol

When to choose

  • you need pub/sub spanning from microcontrollers to data centers
  • you want extremely low wire overhead and latency
  • you need location-transparent queries over distributed storages
  • you're building ROS 2 or edge computing systems

When to avoid

  • you only need a simple message broker like MQTT or RabbitMQ
  • your stack is centered on Kafka-style event streaming
  • you need a mature ecosystem with extensive third-party tooling
  • you require strict license compliance review (dual EPL/Apache licensing)

Facets

library · maturity active

message-queue networking rpc caching serialization middleware microservices iot robotics networking embedded-systems rust python cross-platform embedded windows cli self-hosted pub-sub edge-computing ros2 geo-distributed-storage query low-latency iot-protocol router-daemon messaging real-time linux macos

5 sources

Member repositories

RepositoryRoleHealth v2
eclipse-zenoh/zenohmain99

For agents

markdown · JSON · MCP: product_card(name="eclipse-zenoh/zenoh")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem