Intrinsic Core goes Apache 2.0 — the runtime runs locally

Alphabet's robotics unit gave away the part everyone else rents. Intrinsic announced Intrinsic Core at ROSCon 2026 in Toronto today, released under Apache 2.0: a ROS-compatible, hardware-agnostic real-time control framework plus the planning and perception pieces around it. The open source robotics release matters less for the robots than for what it says about where control layers are heading.

What actually happened

Intrinsic's announcement lists what ships in the box:

• Intrinsic Control — a hardware-agnostic real-time control framework that adjusts a trajectory mid-move from sensor feedback
• Pose estimation built on NVIDIA's FoundationPose
• Motion planning that generates collision-free paths
• Grasp planning that adapts to the gripper
• Simulation via Gazebo, plus camera calibration services
• Intrinsic-ROS drivers pre-configured for supported robots, grippers and cameras

The code is on GitHub at intrinsic-ai/intrinsic-core. Intrinsic also shipped a reference design, the Open Machine Tending Solution, for CNC machine tending on Universal Robots and FANUC hardware. SiliconANGLE reports Intrinsic is aiming at the roughly 92% of U.S. and European fabrication shops with no automation at all — shops priced out by integration cost, not by hardware cost.

The word doing the work in that announcement is local. This is a runtime that runs on the hardware in the building, not a client that phones a platform.

Why a local runtime matters for your business

You probably do not run a CNC cell. Read this as a procurement signal anyway, because the same structure shows up in every AI and automation vendor you are evaluating right now.

Most "platforms" sold to small operators split into two layers: a control layer that has to be fast and present, and a management layer that can live anywhere. Vendors have spent a decade bundling both into a subscription, because the control layer is what makes leaving expensive. Intrinsic just unbundled its own — and it is the company with the strongest incentive not to.

So ask the question on your next vendor call, in exactly these words: what still runs when your service is down? Not "do you have an SLA." Not "is there an offline mode." What is the actual failure behavior of the thing that touches my equipment, my orders, my customers.

Three follow-ups that separate a real answer from a slide:

Where does the control loop execute? If the answer is "our cloud," every network blip is an outage on your floor or in your checkout.

What license covers the part I depend on? Apache 2.0 means you can fork it when the vendor's roadmap stops matching yours. A proprietary SDK with an open wrapper is not the same thing, and vendors describe both the same way.

Can I stand it up without the vendor? Clone, build, run. If that path does not exist in the docs, the open source label is marketing.

Alphabet did not open-source Intrinsic Core out of generosity. It open-sourced it because the integration cost — not the technology — is what has kept this market small, and free infrastructure is how you grow a market you intend to sell into later. That is a fine trade. Just know which half you are getting free.

Sources: Intrinsic, SiliconANGLE, intrinsic-ai/intrinsic-core on GitHub.