Open Source RoboticsRobots, software & learning

Eclipse iceoryx2

Software

Zero-copy, lock-free inter-process communication (IPC) middleware with a Rust core and C, C++, and Python bindings, dual-licensed under MIT OR Apache-2.0. [2] [3]

Installation & first result →Official websiteSource codeGetting started

For
Robotics and automotive systems engineers; Rust/C++/Python perception pipeline developers; Embedded and real-time IPC architects [2]
Hardware
x86_64, aarch64, and 32-bit Linux targets [2]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

Eclipse iceoryx2 is a zero-copy, lock-free inter-process communication (IPC) middleware written in Rust, designed as the architectural successor to classic iceoryx for moving high-volume sensor and state payloads deterministically between local processes. This review inspects main commit 66557500807a7c4c77dc9429f9051c092ad0832b (checked 2026-11-21, workspace version 0.10.999), which is dual-licensed under MIT OR Apache-2.0. Separately, GitHub release metadata lists prerelease v0.10.1 on 2026-11-20; the exact contents of v0.10.1 were not inspected separately, so the configuration and support details below describe the reviewed main checkout. Before integrating iceoryx2 into a robotics stack, check three concrete boundaries: which messaging patterns and language bindings are actually implemented today, what "Tier 2" OS support means, and the Rust toolchain floor. [1] [2] [3] [4]

Is this for you?

Workflows
  • Zero-copy publish/subscribe between local processes
  • Low-latency event signaling
  • Request/response and blackboard service communication
  • Cross-language Rust/C/C++/Python FFI pipelines

[2]

Known limitations
  • Current releases are pre-1.0 (v0.10.1 prerelease as of 2026-11-20); Linux, macOS, Windows, and FreeBSD are currently at Tier 2 ("works with a restricted security and safety feature set") rather than Tier 1.
  • Requires Rust 1.89+ (edition 2024) in the workspace Cargo.toml; QNX 7.1/8.0 are Tier 3 (untested in CI), and Android, bare-metal no_std, and VxWorks are proof-of-concept.
  • Go, Java, Kotlin, Lua, Swift, TypeScript, Zig, and Dart bindings remain planned; C# bindings live in a separate repository that may lag main.

[1] [2] [3]

What you need

Operating system
  • Linux (x86_64, aarch64, 32-bit) — Tier 2
  • macOS — Tier 2
  • Windows — Tier 2
  • FreeBSD — Tier 2
  • QNX 7.1/8.0 — Tier 3 (not CI-tested)

[2]

Languages / runtimes
  • Rust (core)
  • C
  • C++
  • Python

[2] [3]

Dependencies
  • Rust toolchain >=1.89 (edition 2024)
  • OS POSIX / native IPC primitives (Linux, macOS, Windows, FreeBSD, QNX)

[2] [3]

Host computer

Runs on standard x86_64, aarch64, and 32-bit Linux hosts as well as macOS, Windows, and FreeBSD; bare-metal no_std is proof-of-concept.

[2]

Skills
  • Rust (>=1.89, Cargo)
  • C / C++ / CMake or Bazel (for FFI bindings)
  • Python (for Python bindings)
  • Inter-process shared-memory architecture

Inferred from Cargo.toml, README language bindings, and root build files.

[2] [3] · Editorial assessment

Installation & first result

Open the upstream getting-started guide [2]

  • Verify Rust toolchain >=1.89 (edition 2024) for native Rust builds or select the C, C++, or Python FFI binding route.
  • Inspect the repository examples/ directory and The iceoryx2 Book for publish/subscribe, request/response, event, and blackboard patterns.
  • Check the README Supported Platforms table to verify whether Tier 2 security/safety restrictions meet your deployment requirements.

[2] [3]

Installation

Build via Cargo (Rust >=1.89) or CMake/Bazel for C/C++/Python FFI bindings; Yocto recipes available at eclipse-iceoryx/meta-iceoryx2.

[2] [3]

Hardware, models & data

Supported hardware
  • x86_64, aarch64, and 32-bit Linux targets; Yocto recipes via meta-iceoryx2

[2]

Interfaces
  • Rust API (docs.rs/iceoryx2)
  • C API
  • C++ API
  • Python API
  • C# bindings (separate eclipse-iceoryx/iceoryx2-csharp repo)

[2]

Inputs and outputs

Zero-copy shared-memory message transport across publish/subscribe, request/response, event signaling, and blackboard services.

[2]

File formats
  • In-memory zero-copy typed payloads (with iceoryx2-bb/flatbuffers workspace crate available)

[2] [3]

Evaluation

Upstream README links mechanism and architecture benchmark plots measured on Intel i7-13700H / Linux 6.10.10 (rustc 1.81.0, gcc 14.2.1); not independently reproduced in this review.

[2]

Project notes

Messaging patterns and language bindings

The README documents a service-oriented IPC model with publish/subscribe, request/response, and events (low-latency inter-process signaling), while pipeline is marked as planned. Note an internal inconsistency in the inspected README regarding blackboard: the opening bullet list includes blackboard alongside publish/subscribe and request/response, whereas a later paragraph groups blackboard with upcoming features like pipelines. Verify blackboard availability in your target revision or release notes before depending on it. [2]

Core development is in Rust (the workspace Cargo.toml targets Rust edition 2024 with rust-version = "1.89"). In-tree FFI bindings are marked done for C, C++, and Python, with published API references for all four languages. C# bindings are marked done in a separate repository (eclipse-iceoryx/iceoryx2-csharp) with an explicit caveat that they may lag main. Bindings for Go, Java, Kotlin, Lua, Swift, TypeScript, Zig, and Dart are all still planned—so teams needing Go or TypeScript today should not assume ready-to-use wrappers. [2] [3]

Platform support tiers are not yet Tier 1

Upstream's platform matrix distinguishes between implementation completion and safety/security maturity: [2]

  • Done, Tier 2 ("works with a restricted security and safety feature set"): Linux (x86_64, aarch64, 32-bit), macOS, Windows, and FreeBSD. Yocto recipes are maintained separately in eclipse-iceoryx/meta-iceoryx2.
  • Done, Tier 3 (not tested in CI; may or may not compile and run): QNX 7.1 and QNX 8.0.
  • Proof-of-concept: Android (local inter-thread communication only), Bare Metal no_std (events not yet working; memory usage unoptimized), and VxWorks (maintained on an ekxide fork branch).
  • Planned: FreeRTOS, ThreadX, iOS, RTEMS, Redox OS, and WatchOS.

Upstream includes latency benchmark plots comparing mechanisms and architectures on an Intel i7-13700H running Linux 6.10.10 (rustc 1.81.0, gcc 14.2.1); those are vendor-reported figures rather than measurements reproduced by this review. [2]

What we checked

Primary-source repository metadata, README, Cargo.toml, and LICENSE inspection only. No Rust/C/C++/Python builds, IPC benchmarks, or cross-platform tests were executed.

Updates

Upstream last updated
Nov 21, 2026 [1]
Latest release
Nov 20, 2026 [1]
Profile updated
Nov 21, 2026
Sources last checked
Nov 21, 2026
Next review
Feb 19, 2027
Reviewed revision
eclipse-iceoryx/iceoryx2@66557500807a7c4c77dc9429f9051c092ad0832b · software repository

Source files and licenses

Active zero-copy, lock-free Rust IPC middleware with C/C++/Python bindings and permissive MIT OR Apache-2.0 dual licensing.

LayerAvailability / license
softwareavailable · MIT OR Apache-2.0
Cargo.toml declares license = "MIT OR Apache-2.0", backed by root LICENSE-MIT and LICENSE-APACHE files. [3] [4]
documentationavailable · MIT OR Apache-2.0
Repository README and in-tree documentation covered by dual MIT OR Apache-2.0 license; external iceoryx2-book is hosted separately by ekxide. [2] [4]

IPC middleware library; no model weights.

IPC middleware library; no datasets.

Dual licensing and commercial support separation

The workspace Cargo.toml declares MIT OR Apache-2.0, backed by root LICENSE-MIT and LICENSE-APACHE files, allowing adopters to choose either license. Under the supplied LICENSE-MIT text, redistribution requires retaining the copyright and permission notices and the software is provided "as is" without warranty; adopters choosing Apache-2.0 should review the full root LICENSE-APACHE text for its conditions, as only an excerpt was reviewed in this packet. Commercial extensions, consulting, and integration support are offered separately by ekxide IO GmbH, which also hosts *The iceoryx2 Book*. [2] [3] [4]

No Cargo, CMake, Bazel, or Python builds or IPC benchmarks were run in this review. The practical next step for Rust workspace builds is verifying your toolchain meets rust-version = "1.89" (while C, C++, and Python users should consult their binding-specific build requirements, which were not verified here), running one publish/subscribe example from examples/, and confirming whether Tier 2 security/safety features satisfy your robot deployment requirements. [2] [3]

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.8.0-draft.1

Change history