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...

View on GitHub ↗Jump to charts ↓

eclipse-zenoh/zenoh has 3k+ stars and 350+ forks on GitHub, is written in Rust, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 33 minutes ago
Added to GitGenius on September 21st, 2026
Created on January 21st, 2020
Open Issues & Pull Requests: 340 (+0)
GitHub issues: Enabled
Number of forks: 393
Total Stargazers: 3,272 (+1)
Total Subscribers: 32 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.7 days
Mean response time: 88.5 days
90th percentile: 291.3 days
Tracked items: 353

Maintainer activity

11 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "umbrella" is answered fastest, typically in about 2 hours, while "enhancement" waits about 6 weeks. 50% of tracked open issues have had no activity in three months. Only 26% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 212
New in 7 days: 7
Closed in 7 days: 2
Avg open age: 367 days
Stale 30+ days: 185
Stale 90+ days: 148

Recent activity

Opened in 7 days: 6
Closed in 7 days: 2
Comments in 7 days: 12
Events in 7 days: 24

Top labels

  • bug (220)
  • new feature (97)
  • enhancement (40)
  • release (26)
  • umbrella (11)
  • question (9)
  • api fix (8)
  • documentation (7)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Zenoh is a distributed computing platform that unifies messaging, storage, and computation across geographically dispersed systems.

The core problem zenoh addresses is the fragmentation of data infrastructure in modern systems. Applications typically require separate tools for real-time messaging, distributed storage, and query processing, leading to complexity and inefficiency. Zenoh combines these capabilities into a single unified layer by blending traditional publish-subscribe messaging with geo-distributed storage and query functionality. The platform is designed to handle data in motion, data at rest, and computations while maintaining efficiency levels significantly beyond mainstream alternatives.

Zenoh suits projects requiring seamless data flow across edge devices, cloud infrastructure, and on-premises systems. It is particularly valuable for IoT deployments, robotics systems, and ROS2-based applications where latency-sensitive communication and distributed state management must coexist. Organizations should consider zenoh when they need to reduce operational complexity by consolidating multiple data infrastructure components, or when they require the time and space efficiency gains that come from a purpose-built unified platform rather than layering separate systems.

The project demonstrates sustained development activity with regular contributions across its core components. Work spans the protocol implementation, language bindings, and platform-specific optimizations. The codebase shows ongoing refinement of both the messaging layer and storage subsystems, indicating active maintenance of the unified architecture. Documentation and example implementations receive consistent updates alongside feature development.