# eclipse-iceoryx/iceoryx

Eclipse iceoryx™ - true zero-copy inter-process-communication

Repository: https://github.com/eclipse-iceoryx/iceoryx
Canonical: https://ross.abutalabs.com/products/iceoryx
Homepage: https://iceoryx.io
Language: C++
License: Apache-2.0
License Family: permissive
Topics: iceoryx, eclipse, ipc, inter-process-communication, cpp, zero-copy, middleware, pubsub, publish-subscribe, shared-memory, dds, cyclonedds, ros2, autosar-adaptive, request-response, client-server
Last push: 2026-08-18T08:20:24+00:00

## Health v2 (maintenance only)
Score: 94/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 84, longevity 100
- inputs: {"age_days": 2577, "days_push": 15, "days_rel": 106, "gap_med": 11, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2157, forks 488 (observed 2026-08-28T04:06:19.796678+00:00)

## What it is
Eclipse iceoryx is a C++ inter-process communication (IPC) middleware that provides true zero-copy data transfer via shared memory, with publish-subscribe and request-response APIs. It originated in the automotive industry for high-volume sensor data exchange and is used in robotics (ROS2) and other data-intensive systems.

## Use cases
- transfer large sensor data like camera or lidar streams between processes with zero copies
- build low-latency publish-subscribe communication between processes on Linux
- integrate zero-copy IPC into ROS2 or CycloneDDS-based systems
- implement request-response communication between processes using shared memory
- reduce CPU overhead and latency in automated driving or robotics middleware
- share data between processes deterministically for real-time systems

## When to choose
- you need true zero-copy, shared-memory IPC with deterministic latency in C++
- you are on Linux, macOS, QNX, FreeBSD, or Windows and need high-throughput pub/sub between processes
- you are integrating with ROS2 or DDS-based automotive/robotics stacks

## When to avoid
- you are starting a new project - the maintainers recommend iceoryx2, since iceoryx classic is in maintenance mode and will reach end of life after iceoryx2 v1.0
- you need network communication across machines rather than inter-process communication on one host
- you need a language other than C++ without bindings

## Facets
- artifact type: library
- maturity: maintenance
- function: message-queue, middleware, rpc, serialization
- domain: microservices, robotics, autonomous-vehicles, performance, developer-tools
- platform: windows, bsd, cpp, cross-platform
- tags: zero-copy, shared-memory, ipc, pubsub, publish-subscribe, dds, ros2, automotive, autosar-adaptive, request-response, client-server, real-time-systems, real-time, linux, macos

## Member repositories
- eclipse-iceoryx/iceoryx (main) score 94

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:19.796678+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:50:23.778474+00:00, confidence not recorded.
  - readme: https://github.com/eclipse-iceoryx/iceoryx (fetched 2026-08-28T04:06:19.796678+00:00, sha db363482a716)
  - homepage: https://iceoryx.io (fetched 2026-08-29T10:30:20.428599+00:00, sha 2a869584fbd7)
- Data as of 2026-08-30T08:39:29.467469+00:00.