EngineeringThe briefing
Alphabet's Intrinsic released ROS-compatible control, motion and grasp planning under Apache 2.0 at ROSCon 2026. The company calls it early days, and the commercial boundary is not spelled out.
On September 22, 2026, Intrinsic announced Intrinsic Core at ROSCon 2026 in Toronto. Intrinsic is the robotics software company owned by Alphabet. It is releasing core parts of its robot software as open source under the Apache 2.0 license, a permissive license that lets you use and change the code. The code is on GitHub.
Intrinsic's post lists what is inside. There is a control system that works with different robot hardware and can adjust a robot's path while it moves. There is pose estimation, which finds the position of a part, built on NVIDIA FoundationPose. There is motion planning, grasp planning, simulation using Gazebo, camera calibration and ready-made ROS drivers for supported robots and cameras.
The scope is narrower than it sounds. The Robot Report describes the target user as someone who already knows ROS and works with robot arms, not mobile robots or humanoids. Intrinsic's own post calls this early days for its open source work and says users need basic robotics skills.
Some things are not said. Neither Intrinsic's post nor SiliconANGLE spells out which parts of the commercial platform stay closed, what support is offered or what any of it costs. Intrinsic also released an Open Machine Tending Solution, a ready-made reference design that works with hardware from Universal Robots and FANUC. A software license covers code. It does not cover safety certification.
Treat this as a set of ROS packages you will own, not a finished stack. Two things decide how costly a trial is. Pose estimation builds on NVIDIA FoundationPose, so check the GPU requirements against the hardware you have. Real-time control also puts limits on your operating system, which a laptop test can hide. Check the driver list against your actual arms, grippers and cameras first. Pin to specific commits, since Intrinsic calls this early days. Do your first pass in simulation.
Apache 2.0 removes a license negotiation and replaces it with a maintenance job. Open code does not come with support. If it would sit under a production line, decide now whether you will buy support or staff it yourself. Ask Intrinsic which features stay in the paid product, because the announcement does not say. Safety responsibility also does not move. Whoever builds and runs the cell still owns the safety certification. Budget for the assessment, not just the software.
Spend one hour on two documents before touching code: the license and the supported hardware list. Write down which of your robots, grippers and cameras have drivers and what GPU pose estimation needs. Then ask Intrinsic one question: which capabilities stay in the commercial product? Record the answer. Together these decide whether a simulation pilot is worth scheduling, and neither commits you to anything.
Source material behind this briefing. Our practical implications are Ashlr’s interpretation.
This briefing was prepared with AI assistance from the linked sources. The analysis may include interpretation; consult the original sources for complete context. Cover artwork is illustrative.
The briefing
AI-generated illustration
Phantom received new read-only panes for goals, ideas, and library in the verse dock along with owner history paging and triage updates. Other projects added test coverage only.
EngineeringThe briefing
Phantom pull requests add read-only fleet health checks and improve merge reconciliation, latency reporting and worktree cleanup. Documentation updates cover multiple products including Locus, Lexicon and Ashlr Stack.
EngineeringAshlr release
Ashlr Stack released version 0.3.6. Pull requests added regression tests for device codes, HTML entities, installers, regex replacements, and autofix rules in multiple projects.
