Explicit boundaries
Applications enter through named APIs, skills, or bounded streaming sessions.
PLEXA Developer Platform
Connect your software, robotics stack, or simulation through explicit, governed HorstOS interfaces.

runtime.connect()robot.state.poseskills.execute()Choose your path
Begin with the interface that matches your application. Every path converges on the same controlled Runtime and safety boundary.
Connect applications to governed commands, I/O, robot state, and status streams.
REST · WebSocket · ProtobufUse the PLEXA robot model with RViz and MoveIt while the controlled Runtime bridge evolves.
Robot description · RViz · MoveItDevelop against the Runtime boundary without requiring access to physical hardware.
Local Runtime · digital twinConnect teleoperation, motion tracking, VLA systems, or partner controllers through bounded sessions.
Realtime targets · feedback · watchdogExpose selected PLEXA capabilities as governed skills and tools for task-level intelligence.
Capabilities · skills · MCP toolsIntegration principles
Protocol compatibility alone does not grant Runtime control compatibility.
Applications enter through named APIs, skills, or bounded streaming sessions.
State, telemetry, and command results remain part of every integration path.
External software never bypasses Runtime, motion control, safety, or hardware boundaries.