Open Source Robotics

A curated collection of high-quality open source robotics projects, tools, and software to propel the robotics community forward.

Hiroz

Pure-Rust ROS 2 on Zenoh, wire-compatible with standard nodes and no ROS install

License

Apache-2.0

Overview

Hiroz is a ROS 2 implementation written in Rust directly on Zenoh, built by the ZettaScale team that makes Zenoh. A node written against it speaks the same wire protocol as a standard ROS 2 node running the rmw_zenoh middleware, so the two see each other's topics, services and actions — but the Hiroz node needs no ROS installation, no colcon workspace and no setup.bash. It is a Cargo dependency, with the standard message types bundled. Publishers, subscribers, services, actions, parameters, lifecycle nodes and shared-memory transport are implemented, with Python and Go bindings, a command-line toolkit called hu, and an experimental rmw implementation so existing C++ and Python nodes can run on the Rust core.

The distinction that matters is between Hiroz and rmw_zenoh. rmw_zenoh is a middleware plugin: it swaps DDS for Zenoh underneath an ordinary rclcpp or rclpy program, and the application still depends on a full ROS 2 install. Hiroz removes the install. It is an independent client library that reimplements the ROS 2 graph — node naming, namespaces, remapping, discovery key expressions, type hashes — on the Zenoh API, and stays wire-compatible with rmw_zenoh so it can join an existing system rather than replace it. The authors' own feature comparison is the most useful page to read: it marks where Hiroz matches ROS 2, where it goes further — pull-model subscribers, dynamic schema-driven messages, Protobuf encoding, a Humble-to-Jazzy bridge that neither DDS nor rmw_zenoh offer — and where it falls short.

Distribution support is handled by compile-time feature flags. Jazzy is the default; Kilted, Lyrical and Rolling are supported; Humble builds but without real type hashes, because Humble never had them, so type safety is not checked during discovery there. The experimental rmw-zenoh-rs, which lets unmodified C++ and Python nodes run on the Rust stack, needs Jazzy or later.

The repository describes itself as experimental and it means it. One developer has written the great majority of the code, with contributions from ZettaScale colleagues including its founder, and there are three tagged releases, the latest in August 2026.

Why it matters

Getting a ROS 2 node running has always meant installing ROS 2 first, which is the reason a lot of embedded, web-adjacent and Rust-first teams never join a ROS system at all. Hiroz is the first serious attempt to cut that dependency without forking the ecosystem: it comes from the people who make Zenoh, targets the Zenoh middleware that ROS 2 itself now ships, and stays on the wire so a Rust service and a stock rclcpp node can talk to each other. If it holds up, it changes who can put a node on a ROS graph.

Problem it solves

Writing something that talks to a ROS 2 system normally means depending on a full ROS 2 installation and its build tooling. Hiroz lets a Rust, Python or Go program join the same graph over Zenoh with a single library dependency and nothing installed system-wide.

Key takeaways

  • An independent ROS 2 client library in Rust, built directly on the Zenoh API rather than as a middleware plugin
  • Wire-compatible with standard nodes running rmw_zenoh, so it joins an existing ROS 2 system instead of replacing it
  • No ROS installation needed — a Cargo dependency with the standard message types bundled
  • Pub/sub, services, actions, parameters, lifecycle nodes and shared memory are implemented, with Python and Go bindings
  • Goes beyond stock ROS 2 in places: pull-model subscribers, dynamic schema-driven messages, Protobuf encoding and a Humble-to-Jazzy bridge
  • Jazzy by default, with Kilted, Lyrical, Rolling and Humble selected by feature flags
  • Built by ZettaScale, the company behind Zenoh, under Apache-2.0

Who it is for

  • Rust developers who want to talk to a ROS 2 system without installing ROS 2
  • Teams already moving to the Zenoh middleware who want a native Rust client on the same wire
  • Anyone who needs to bridge Humble and Jazzy systems during a migration
  • Embedded or edge developers for whom a full ROS 2 install is too heavy
  • Go and Python developers who need ROS 2 messaging from outside a colcon workspace

Limitations

  • Explicitly experimental — the authors make no guarantees and the API should be expected to change
  • Only interoperates with nodes running rmw_zenoh; a system still on the default DDS middleware will not see it
  • No /rosout logging and no /clock topic yet, so external simulation time is not supported
  • Deadline and liveliness QoS events are unavailable, a limitation Zenoh shares with rmw_zenoh
  • On Humble there are no real type hashes, so type mismatches are not caught during discovery
  • Executors, waitsets, composable nodes and intra-process communication exist only in the experimental rmw-zenoh-rs, which needs Jazzy or later
  • One developer wrote the great majority of the code, which is a real bus-factor risk for a middleware layer

This website requires JavaScript to function properly. Please enable JavaScript to explore our collection of open source robotics projects.