Intrinsic Core Open-Sources a Local ROS 2 Runtime for Industrial Robotics


Intrinsic has released Intrinsic Core, an Apache-2.0 open-source robotics stack that runs locally and combines a runtime, SDK, hardware abstraction, real-time control, motion planning, perception and machine-learning inference. The project is ROS 2-compatible and targets industrial robotics developers building systems that must move from simulation and perception into hardware execution.

The public repository lists Ubuntu 24.04 LTS or Ubuntu 26.04 LTS as the primary operating-system prerequisites, with Ubuntu 22.04 LTS also supported, and specifies ROS 2 Lyrical Luth. Intrinsic describes the runtime as a native k3s-based containerized environment and the core implementation is primarily C++ with Bazel-based development.

The release exposes a substantial part of Intrinsic's robotics infrastructure as reusable local software, giving developers a code-accessible path across runtime, perception, planning and control. It also arrives during ROSCon 2026, where ROS 2 Lyrical and accelerated physical-AI pipelines are major ecosystem themes.

What Intrinsic Core includes

The repository separates the stack into modules with distinct deployment roles:

Module Role
intrinsic_runtime Local execution environment built around a k3s containerized runtime, process lifecycle, scheduling and application-state synchronization
intrinsic_control (ICON) Real-time motion and hardware coordination, trajectory interpolation, kinematics and a hardware abstraction layer
intrinsic_motion_planning Collision-free Cartesian and configuration-space path generation, constraints and motion blending
intrinsic_perception Camera and point-cloud interfaces plus NVIDIA FoundationPose support for 6-DoF object pose estimation
intrinsic_inference Local accelerated ML inference and model-serving infrastructure
intrinsic_sdk Interfaces, serialization helpers and data structures for custom skills, hardware assets and execution nodes
intrinsic_hardware Drivers, manifests and integrations for industrial peripherals
intrinsic_kinematics Manipulator kinematics and solver library

Intrinsic says ICON can switch controllers within a control cycle using live sensor feedback. Its hardware abstraction layer is intended to let applications move across robot arms, grippers and fieldbus I/O without rewriting the application around each vendor-specific interface.

ROS 2 interoperability and local deployment

Intrinsic Core is designed to interoperate with ROS 2 while providing its own integrated runtime and APIs. That is useful for teams that already depend on the ROS ecosystem and want an integrated execution layer spanning perception, planning, control and hardware.

The current repository specifies ROS 2 Lyrical Luth. Intrinsic also publishes related repositories for MoveIt 2 integration, local inference, hardware modules, shared-memory IPC and ROS camera drivers.

The stack is explicitly local: the repository describes intrinsic_inference as an edge inference service and the runtime as a local execution environment. That makes the release relevant to factory and lab systems where sensor, control and model-serving paths need to remain close to the robot.

Perception, planning and control in one stack

The perception module includes support for NVIDIA FoundationPose for 6-DoF pose estimation. Detected object poses can feed the planning and control layers through the stack's standardized APIs.

Motion planning handles collision-free paths across Cartesian tasks and wider configuration-space movement. The control layer then provides kinematics, trajectory interpolation and deterministic hardware coordination. The architecture is aimed at reducing the integration work between separate perception, planner and robot-driver systems.

Intrinsic also publishes grasp planning, simulation and calibration capabilities around the Core environment. These components are especially relevant to manipulation workloads where object pose, collision constraints and gripper behavior change between parts or workcells.

Open Machine Tending Solution provides a reference deployment

Alongside Core, Intrinsic has published an Open Machine Tending Solution (OMTS) as an open-source reference design. It packages assets, skills and deployment patterns for CNC machine-tending workflows and is intended as a starting point that can be adapted to different industrial hardware.

That reference implementation gives developers a concrete end-to-end evaluation path: teams can inspect how the runtime, robot abstraction, perception and application logic are assembled for a production-style task.

License and current maturity

The Intrinsic Core repository is licensed under Apache License 2.0. GitHub records the repository as created on September 8, 2026, with the public code actively updated on September 22.

The repository identifies Intrinsic Core as an Intrinsic project and states that it is not an officially supported Google product. Production evaluations should validate hardware compatibility, real-time behavior and operational support against the target robot, fieldbus and safety architecture.

Deployment fit

Intrinsic Core is most relevant to teams building industrial manipulation or physical-AI systems that need a local runtime and want ROS interoperability with an integrated stack. Its strongest practical differentiator is breadth: real-time control, hardware abstraction, perception, planning, inference and a reference industrial application are available from the same project family.

For existing ROS deployments, the immediate evaluation questions are concrete: whether the target system can move to ROS 2 Lyrical, whether supported hardware interfaces cover the workcell, and whether ICON's control model fits the application's real-time and safety requirements. The Apache-2.0 release makes those questions testable directly from the code.

Sources