Skip to main content

Roadmap

What OpenRoIS has built and what comes next, for an open-source middleware implementing the OMG RoIS Framework 2.0. The roadmap in the repository is the status of record, and this page copies it.

Until v1.0, OpenRoIS is alpha, pre-1.0, with an unstable API. The milestones are in order and carry no dates: each one is released when it is ready.

Milestones​

MilestoneStatusWhat it delivers
v0.1.0 (November 2026)ReleasedEvery package at 0.1.0, released together. A physical Reachy Mini and a physical Kachaka behind one gateway, driven by a scripted application, the OpenRoIS Inspector, and an AI agent. A physical and a simulated Reachy Mini behind one gateway under one application
v0.2PlannedRoIS conformance: components declared by XML profiles at run time, the types checked against the normative RoIS files on every change, a test suite that adapter authors run against their own adapter, and a conformance claim. Applications and engines that recover when a gateway or an adapter restarts
v0.3PlannedA physical robot and a virtual avatar behind one gateway, controlled by one application that does not know which is which
v0.4PlannedAuthentication at the WebSocket upgrade and authorization per RoIS operation. Until then, a reverse proxy in front of the gateway terminates TLS (Deployment)
v0.5PlannedMedia for the AudioStreaming and VideoStreaming components. OpenRoIS does not prescribe a media transport: a streaming component returns a descriptor of its stream, and an optional WebRTC integration serves deployments that have none
v1.0PlannedA stable API, and the first release with semantic versioning guarantees. It stands on the milestones above: the conformance claim, authentication, and reference adapters for two robots and a virtual avatar, on Linux, Windows and macOS
Beyond v1.0Beyond 1.0The remaining basic RoIS HRI Components, each released when it is ready. A registry of community components and adapters, and a Hub that shows operators the adapters, sessions and health of a deployment

The Stack, Bottom Up​

Each layer builds on the one below it.

LayerPackagesRole
Interfacesopenrois-interfaces (PyPI), @openrois/interfaces (npm), C# types inside the Unity packageThe RoIS types and method catalog that every other layer speaks. Authored once in Python and generated through JSON Schema into TypeScript and C#, with all 18 normative profiles and an XML profile codec, cross-checked against the OMG machine-readable files
Engineopenrois-engineOne recursive engine for both the main and the sub HRI Engine roles. It carries the RoIS interfaces, profiles and common messages: sessions, binds, command sequences with concurrent branches, timeouts, events and the error channel, as rois-reference §16 records them. It serves and consumes RoIS over WebSocket, so a gateway can sit under a gateway, and grows to components declared by XML profiles at run time
Engine processesopenrois-gateway; the adapter processThe engine as deployable processes. The gateway is the main HRI Engine that applications connect to, configured by YAML, environment or flags and shipped as a container image with Docker Compose. An adapter process is a sub HRI Engine that hosts the components of one robot or agent, configured by adapter.yaml
Componentsopenrois-components-core; each robot's package in its adapter repositoryThe RoIS HRI Components themselves. The component SDK (@component, @command, @query, @event, resources, ROS 2 support) turns a capability of a robot or a virtual avatar into a component, and each adapter's package builds on it. The Reachy Mini adapter is the reference, run on the real robot and in simulation, and the Kachaka adapter serves a second robot over its gRPC API
Client SDKs@openrois/sdk (npm), openrois-sdk (PyPI), org.openrois.sdk (Unity, by Git URL)How service applications speak RoIS from JavaScript, Python and Unity, with typed models over the wire protocol and one conformance list that all three pass
Applicationsopenrois-mcp; the OpenRoIS InspectorReady-made service applications: an MCP server that lets AI agents drive the robots behind a gateway, and the OpenRoIS Inspector, which shows the engines and components behind a gateway and drives them as a service application does. A Hub for operators follows beyond v1.0

Versioning​

  • The packages share their major and minor version and are released together under a project tag such as v0.1.0. A package may carry its own pre-release or patch number in between.
  • 0.x releases may break the API without notice.
  • v1.0 is the first release with semantic versioning guarantees.

Contributing​

An adapter for a new robot, with its components in its own repository, is the natural entry point. See Contributing, or open an issue to propose a change to the roadmap. All work is released under the Apache-2.0 license.