There is a number that keeps doubling, and nobody outside a handful of data centers fully appreciates what it means.
In Q1 2024, the total tracked AI compute capacity across the worldβs major technology players stood at roughly 2.5 million H100-equivalent units. By Q4 2025 β eight quarters later β it had reached 21.3 million. An 8.5Γ expansion. Not 8.5% growth. Not 85%. Eight and a half times.
This is not a build. It is a structural transformation of who controls the physical substrate of the next economy. And the patterns visible in that data β who is building, at what pace, with whose chips, toward what architecture β reveal something deeper than a hardware procurement story. They reveal the strategic intentions of the five or six organizations that are quietly competing to own the AI infrastructure β as explored in the economics of AI compute infrastructure β layer for the next decade.
FREE NEWSLETTER
Get AI Strategy Intelligence Daily
Join 90,000+ strategists. Business modelanalysis, AI maps, and earnings deep dives β free.
Gennaro Cuofano is a CRO and tech executive who has worked in AI since late 2015, starting with bringing NLP, natural-language generation, voice and chatbot products to the marketing industry. His background is in law and finance: he holds a Master's degree in Law and an International MBA with an emphasis on corporate finance (LUISS Business School and the University of San Diego, 2012), and worked as a financial analyst at a real-estate investment firm in San Diego and as an assistant controller. His work focuses on business model strategy, business engineering and, more broadly, structural analysis: how companies make money, read from their own filings. He created FourWeekMBA and leads research there and at The Business Engineer, his newsletter on AI and business strategy, with over 95,000 subscribers and more than 1,000 published analyses. His writing has also appeared on Entrepreneur (for example, How to Digitize a Family Business in Europe) and HackerNoon. Find him on LinkedIn and Substack. See how we source.
