Eclipse Zenoh on Ubuntu 24.04 LTS

Azure Application Infrastructure

Eclipse Zenoh, a router that carries publish subscribe, query and persistent storage for edge, IoT and robotics estates over one protocol.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Overview

Eclipse Zenoh unifies data in motion, data at rest and computation in a single protocol. Producers publish on key expressions such as sensors/site-a/temperature and every subscriber whose expression matches receives the value, with wildcards making the routing declarative rather than something you wire up by hand. The same namespace also answers queries on demand, so request and response live alongside streaming instead of needing a second stack, and a storage plugin persists whatever is written under a chosen key expression so later queries are answered from disk. This image ships zenohd, the router: the infrastructure node that peers and clients connect to, that routes their traffic, answers their queries, holds their stored data, and federates with other routers to span sites. It is the piece you deploy once and point everything else at, and it is deliberately lean, measured peaking at 28 MB of memory while carrying four thousand messages.

Why the cloudimg image

The configuration Zenoh ships by default accepts any client on any key expression with no authentication at all, which is reasonable on a laptop and unacceptable on a public network, so this image replaces it. Every session must authenticate, the credentials are generated on your own machine at first boot rather than baked into the image, access control is enabled with a default of deny, and a second least privilege identity is confined to its own subtree. Multicast discovery is switched off, the REST plugin is bound to loopback because plugins are not subject to the access control rules, and the router refuses to start at all if it finds a credential or private key that upstream published in its own test suite. Every one of those claims is proven on each fresh machine by an end to end check that publishes and subscribes between separate processes, reads stored data back after restarting the router, and confirms that unauthenticated and wrong credential clients are both rejected. A paired deployment guide and 24/7 support are included.

Common uses

  • Robotics and autonomous vehicle fleets sharing telemetry and commands
  • Industrial and edge estates federating sites through one bus
  • Applications needing streaming, query and storage in a single namespace