Transport-level routing for MCP/ACP protocols
stdio Bus
stdio Bus is the runtime platform for agent systems. Route, execute, and operate agent workloads with deterministic transport, session control, streaming, and production-grade lifecycle management — across ACP, MCP, and beyond.
How the Stack Works
Layer 1
Kernel — Deterministic Transport
The Kernel routes messages between clients and workers with deterministic, auditable behavior. It provides the transport foundation that every other layer builds on.
Layer 2
Platform — Specification-Driven Systems
The Platform extends the Kernel into a complete environment for designing, building, and operating agent systems. Define behavior through specifications, then let the platform handle orchestration.
Layer 3
Registry — Reusable Components
The Registry provides a catalog of published workers, modules, bridges, and templates. Teams share and discover building blocks instead of rebuilding from scratch.
Layer 4
SDK — Integration Libraries
Language SDKs and integration libraries let you connect clients, workers, and tools to the ecosystem in your preferred language and framework.
Layer 5
Labs — Research and Exploration
Labs is where experimental protocol work, benchmarks, and future platform directions take shape before graduating into the production stack.
The Ecosystem
A layered stack where each component builds on the one below it. The Kernel provides the deterministic foundation; everything else extends from there.
Platform
Design, build, and operate agent systems
Kernel
Route messages deterministically
SDK
Integrate clients, workers, and tools
Registry
Reuse workers, modules, and bridges
Labs
Research, benchmarks, and experimental protocol work
Use Cases
Multi-Agent Orchestration
Route messages between multiple agent workers with deterministic session affinity. Each agent maintains its own state while the transport layer handles routing and backpressure.
IDE and Tool Integration
Connect development tools, IDEs, and CLI clients to agent systems through a unified transport layer. Clients connect once and reach any worker in the ecosystem.
Specification-Driven Development
Define agent behavior through formal specifications, then deploy workers that conform to those specifications. The platform validates conformance at runtime.
Reusable Agent Components
Publish and discover workers, modules, and bridges through the Registry. Teams share building blocks instead of rebuilding common patterns from scratch.
Cross-Platform Agent Systems
Build agent systems that work across languages and frameworks using the SDK. Integrate clients and workers in your preferred technology stack.
Production Workloads
Run agent systems in production with deterministic routing, auditable message flows, and built-in backpressure management. No surprises at scale.
Where Do You Want to Start?
Kernel
Route messages deterministically
Platform
Design, build, and operate agent systems
Registry
Reuse workers, modules, and bridges
SDK
Integrate clients, workers, and tools
Labs
Research, benchmarks, and experimental protocol work