Eclipse Zenoh

P2P Protocol

A pub/sub/query protocol that unifies data in motion, data at rest and computation. It combines publish/subscribe with geo-distributed storage, queries and computations, while keeping time and space efficiency the project describes as well beyond mainstream stacks, with a five-byte wire overhead. Applications use first-class abstractions for pub/sub, storages and queryables, with several levels of reliability, dynamic discovery, fragmentation and batching. The Rust crate is the reference implementation of the protocol and the libraries for other languages are bindings to it, apart from a pure-C implementation for microcontrollers (zenoh-pico). It is an incubating project of the Eclipse Foundation .

Foundation
Links
Visit Website See this tool in the graph Suggest an edit

Details

License Dual licence: Eclipse Public License 2.0 and Apache License 2.0, at the user's option. https://github.com/eclipse-zenoh/zenoh (Rust reference implementation), with bindings and zenoh-pico in sibling repositories
Dev Status 🟢 Active
Owner Eclipse Foundation (Eclipse Zenoh, an incubating project)
Governing Body Eclipse Foundation (Eclipse Zenoh incubating project)
Country Not stated by the project.
Start Year 2020
Stack Rust core and reference implementation; bindings for other languages; zenoh-pico in C for constrained devices
Funding Eclipse Foundation sponsorship, with ZettaScale Technology also listed as a sponsor on the community page
Last Investigated Oct 29, 2026

Use Case Domains

Platform Evolution & Sovereignty

Affordances

Local-first storage Data portability

P2P Protocol Attributes

Origins Unify data in motion, at rest and in computation across devices, edge and cloud with very low overhead, for robotics, IoT and distributed applications
Database N/A
Query Language N/A
Data Formats Zenoh wire protocol with compact binary encoding; payloads are opaque bytes with optional encoding metadata
Collaborative Live Editing N/A
Rich Text Editing N/A
Mobile Support Library-level; bindings and zenoh-pico for constrained devices
Web Support Through a bridge and bindings listed on the project site; the cited sources give no detail
Native Apps Library-level, plus routers and tools
Terms Free and open source: the project's site says it is free and open source and always will be
Funds Not stated by the project.
Based On Original protocol design; pub/sub, queries and storage semantics defined by the project
P2P Architecture The site describes dynamic discovery and geo-distributed storages; the cited sources do not describe the connection topology (peers, clients and routers)
Overlay Network Yes, in the sense of a Zenoh network of nodes with geo-distributed storages; the cited sources give no topology detail
Content Addressing No.
Local-First Not a local-first data layer; it supports data at rest through storages that can sit close to producers
E2EE Not stated by the project.
CRDTs Lib No: not a CRDT library.
Byzantine Fault Tolerance Not stated by the project.
Signature Not stated by the project.
Permissions Access-control configuration is described in the project documentation; the cited sources give no detail
Semantic Web Compatibility N/A: no RDF, JSON-LD or SPARQL layer.
Smart Contract N/A: no ledger or smart-contract component.
Protocol Stack Position Application and network layer protocol that runs over several transports
Asset / Value Embedding None: no token or value-transfer mechanism.
Protocol Maturity / Standardization Reference implementation and published protocol under Eclipse incubation; no standards-body specification