The Missing Robot ECU - and Who Will Build It
McKinsey just published a supply chain analysis of humanoid robotics. Everyone quoted the actuator cost data.
I think the most important sentence in the report was buried three sections in. And it names a gap that no one has filled yet.
Last post, I ended with a line that I keep thinking about.
"Models get commoditized. Infrastructure scales."
I was talking about the data layer. But the same logic applies one level deeper — at the layer where data meets hardware, where decisions become motion.
McKinsey published an analysis of humanoid robotics supply chains in April. The headline finding everyone quoted was about actuators: they account for 40 to 60 percent of the total hardware cost and remain the most constrained component in the stack. Fair enough.
But I think the most important sentence in that report was buried three sections in.
"There is no standardized, safety-certified robot ECU analogous to an automotive engine control unit."
That one sentence tells you more about where the durable opportunity lives than any bill-of-materials breakdown.
Here is the analogy that matters.
In the 1970s, every car manufacturer built its own engine control logic from scratch. Custom hardware, custom software, hand-integrated for each platform. That was not a strategic choice. It was the only option available. No standard existed.
Then Bosch and Siemens built the ECU. Not a better engine. A control layer that abstracted engine management into a standardized, certifiable module. By the 1990s, nearly every production vehicle on earth ran on one. The companies that defined that interface became Tier 1 infrastructure suppliers to an industry worth trillions.
The automotive ECU was not invented after car production scaled. It was invented before, during the exact window when volumes were approaching but architectures had not yet locked.
That window is when standards form.
McKinsey calls the current moment the "pre-modular phase."
Every humanoid OEM today is doing what car companies did in 1975. They are building the compute and control stack from scratch because they have no choice. A GPU board for perception. Distributed joint controllers. Custom middleware stitching it together. Hand-coded safety logic.
McKinsey's language is precise on why:
"OEMs are forced into vertical integration or close co-development, not because they have a strategic preference for keeping manufacturing in-house, but because no viable supplier options exist."
This is not an engineering failure. It is a market structure problem. The components exist. The integration layer and certification framework do not.
McKinsey classifies the compute and control supply chain as a "systems bottleneck" — not a capacity bottleneck. The chips are available. The missing piece is the platform that integrates them into something a production robot can actually certify and deploy.
And here is the thing about systems bottlenecks: they do not wait for the rest of the market to catch up. They resolve when someone builds the missing layer. Then that layer becomes infrastructure.
This window is specific and closing.
Three conditions drive the shift from vertical integration to platform ecosystems: predictable volumes, stable architectures, and converging interface standards.
VC funding in robotics hit $40.7 billion in 2025, three times the 2023 level. China committed a $138 billion state fund. The first condition is arriving. The second is starting to stabilize around a few dominant form factors.
The third — converging interface standards — does not emerge on its own. It gets defined by the first platform with enough adoption to become the de facto standard.
McKinsey's key line: "Design successes at the prototype stage convert into production incumbency once architectures stabilize and volumes scale."
The standard gets set during the pre-volume phase. Then it locks in. That is exactly how the automotive ECU became infrastructure. That is exactly the moment we are in right now for physical AI compute and control.
The pattern is now consistent.
The models are getting good. The Slow Brain is being solved, the data infrastructure is being capitalized, and the capital is following fast.
What is not built yet is the layer that connects all of it to reliable physical deployment. The real-time control platform. The missing robot ECU.
The company that builds it will not just ship a product. It will occupy the position that Bosch and Siemens hold in automotive. The compute control plane of an entire generation of autonomous physical systems.
I am working on exactly this problem right now. More to come.
What do you think? Is the control standardization race already decided — or still wide open?
Reach me at arif@faris-capital.com
This thesis was originally published on LinkedIn. Join the discussion, add your thoughts, and follow for regular updates.
View on LinkedIn