EIPC — Secure Inter-Process Communication
EIPC is the secure communication fabric that connects every EoS component — a capability-based message bus with HMAC-SHA256 authentication, predictable scheduling, and zero-copy fast paths.
What EIPC is
EIPC extends the EoS capability model out into IPC: every connection is an unforgeable capability handle, every message is HMAC-authenticated, and every queue has a guaranteed latency budget enforced by the scheduler.
It acts as the connective tissue between EoS, EAI, ENI, eApps, and external services — same wire format whether the peer is a thread, a process, a container, or a remote node.
Features
The shape of EIPC at a glance.
Capability Model
Unforgeable connection handles; no ambient authority, no global namespace.
HMAC-SHA256 Authentication
Every message signed; tampering and replay attacks rejected at the bus.
Predictable Latency
Per-channel latency budgets enforced by the EoS scheduler — no priority inversion.
Zero-Copy Fast Path
Shared-memory ring for large payloads when both peers live on the same node.
Streaming & Request/Reply
Both message-passing styles supported; back-pressure first-class.
Cross-Node Transport
Same API over loopback, UART, USB, Ethernet, Wi-Fi, or BLE.
Tracing & Replay
Per-channel structured tracing; deterministic record / replay for debugging.
Quota Enforcement
Per-process bandwidth and queue-depth quotas — no chatty app starves the bus.
Language Bindings
C, C++, Go, Rust, Python, Dart bindings ship in lock-step with the core.
Open source on GitHub
EIPC is Apache-2.0 licensed and developed in the open. Issues, discussions, and pull requests welcome.
In the EoS stack
EIPC is the highlighted layer below.
Pairs well with
Sibling components that EIPC commonly works alongside.
Ready to build with EIPC?
Start with the docs, browse the source, or join the community.