Broadcom reportedly won't build OpenAI's custom chip unless Microsoft buys 40 percent of them
Source published ·Modelwire updated
Original coverage: The Decoder ↗·How Modelwire adds context

The development
OpenAI's push to build proprietary AI chips faces a critical inflection point as Broadcom demands Microsoft absorb 40 percent of production volume before committing to manufacturing. The $18 billion first phase has exposed a structural tension in the AI supply chain: chip makers won't shoulder demand risk alone, forcing AI labs to secure downstream buyers or abandon vertical integration. This signals how capital constraints and manufacturing dependencies are reshaping the competitive dynamics between OpenAI, Microsoft, and hardware vendors, with implications for who controls the infrastructure layer of frontier AI.
Modelwire’s AI-generated summary of coverage from The Decoder.
Modelwire analysis
Analyst takeOur AI-generated reading of the wider context and the next developments to watch.
The Broadcom condition reframes this less as a chip strategy story and more as a test of whether Microsoft will deepen its OpenAI commitment at a moment when that relationship is already under strain. The 40 percent volume guarantee is effectively a forcing function: Microsoft either validates OpenAI's infrastructure independence or quietly signals it won't.
This connects directly to the pattern we've been tracking around Microsoft's posture toward AI infrastructure. The VS Code Copilot attribution incident covered in early May showed Microsoft normalizing AI integration on its own terms, often without surfacing the costs or trade-offs to partners. Here the dynamic inverts: Microsoft is being asked to absorb risk rather than distribute it. The broader context is a supply chain where no single party wants to hold the bag on speculative capacity, which mirrors the bifurcation noted in our coverage of the US-China AI race, where cost discipline and capital exposure are becoming as decisive as raw capability.
Watch whether Microsoft publicly confirms or denies the 40 percent commitment within the next two earnings cycles. A confirmation locks in the dependency and tells you vertical integration is real; silence or denial suggests OpenAI needs a different anchor buyer, which reopens the question of who actually controls its infrastructure roadmap.
This interpretation is generated from the summary above and the archive coverage cited below. Our methodology · Report an error
Coverage behind this analysis
These archive entries ground the connection in our analysis. They are ordered by source publication date, with links to our coverage and the original sources.
·The Decoder
Microsoft caught sneaking "Co-Authored-by Copilot" into VS Code commits - even with AI off
Microsoft embedded AI attribution metadata into Visual Studio Code commits without user consent, persisting the practice even when Copilot was disabled. This reveals a pattern of opaque AI integration in developer workflows and raises questions about whether users truly control AI involvement in their tools. The incident exposes tension between Microsoft's push to normalize AI…
MentionsOpenAI · Broadcom · Microsoft · Sachin Katti
How this coverage is produced
Modelwire uses AI to generate summaries and context from source headlines, snippets, and selected archive coverage. Automated checks do not verify every claim, and items are not routinely reviewed by a person before publication. Zacaria Solis operates the site. Read the linked source for the full evidence and report errors through our corrections process.
Modelwire summarizes, we don’t republish. The full content lives on the-decoder.com. If you’re a publisher and want a different summarization policy for your work, see our takedown page.