Alphabet's Intrinsic open-sources robot control under Apache 2.0

Read this as a set of ROS packages you will own and maintain, not a stack that arrives configured. Two dependencies decide how expensive a trial is: pose estimation builds on NVIDIA FoundationPose, which carries GPU assumptions you should confirm against hardware you already have, and a real-time control framework implies host operating system and kernel constraints that a laptop test will hide. Check the driver list against your actual arms, grippers and cameras before planning any integration, because an unsupported gripper is the difference between a week and a quarter. Pin to specific commits: Intrinsic calls this early days, and an early repository moves under you. Do the first pass entirely in simulation.

Apache 2.0 removes a licence negotiation and replaces it with a maintenance obligation. A permissive licence implies no support commitment, so if this code would sit under a production cell, decide now whether you are buying support separately or staffing the maintenance yourself. The question to put to Intrinsic before any migration planning is which capabilities stay inside the commercial product, because the announcement does not say, and a path off a paid platform cannot be inferred from an open repository. Safety responsibility does not move either: functional-safety certification for a cell remains with whoever integrates and operates it, however the control software is licensed. Budget the assessment, not only the software.