Thesis · Hyperscalers, Cloud & Compute Services

Will combined 2027 capex from Microsoft, Alphabet, Amazon, and Meta grow less than 10% year over year?

The AI buildout may be outrunning real demand. This tracks whether the four biggest cloud spenders sharply slow their capital spending growth in 2027, signaling a digestion phase.

6 dated tests · 0 resolved · next on

The tests More theses in Hyperscalers, Cloud & Compute Services

Who is on each side

The two sides.

Each side in DeepStack’s words, then the voices who argue it, attributed and paraphrased, dated where the date is known. A voice links to its page on DeepStack where one exists.

The case for yes

The buildout overshoots demand

Combined 2027 capital spending across Microsoft, Alphabet, Amazon, and Meta grows by less than 10% year over year, a sharp deceleration from the 30-40%+ pace seen in 2025 and 2026. Capacity, power limits, and efficiency gains caught up to paying AI demand, pushing companies into a digestion phase marked by fewer new campus starts, slower server orders, and guidance cuts across multiple quarters. A related view holds that if chips, people, and power were in infinite supply the market would already show overcapacity, implying that once those supply constraints ease, spending growth settles back toward demand and decelerates.

The case for no

The buildout keeps outpacing capacity

Combined 2027 capital spending across the four companies grows 10% or more year over year, showing no major slowdown. One voice argues that no hyperscaler can afford to slow down alone, since slowing risks losing power, chips, talent, model partners and customers while scarce capacity secured by one firm stays unavailable to others, keeping the buildout pace intact. A related voice notes that fast diffusion lets capex spenders observe how quickly new capacity gets absorbed, reinforcing continued aggressive sizing of spend.

5 voices

The buildout overshoots demand

  1. First Pacific Advisors

    Hyperscalers and specialists are spending massively on data center buildout based on projections of AI demand, but if actual demand growth does not match the buildout pace or if compute prices collapse faster than anticipated, the aggregate capital…

  2. Greenwood Investors LLC

    When investment is accelerated beyond historical precedent and relies on leverage, the resulting supply expansion cannot be absorbed by underlying demand growth, creating inevitable overcapacity and disappointed returns.

  3. Prof G Markets

    Fast-built capex cycle unwinds at the speed it built

  4. Geo Chen

    Shortage flips to compute glut via efficiency gains

  5. Daniel Romero

    No hyperscaler can afford to slow down alone: slowing risks losing power, chips, talent, model partners, customers and the next computing platform while AI threatens their core cash-cow businesses; supply scarcity means capacity secured by one is…

5 voices

The buildout keeps outpacing capacity

  1. Barry Ritholtz

    Ankur Crawford argues that if there were an infinite supply of chips, people and power, the market would already be in overcapacity because everyone would build as fast as they wanted; instead, the shortage of chips, workers like plumbers and…

  2. Oguz Erkan

    Earlier booms busted because diffusion trailed the mobilization of capital, leaving owners unable to extract expected benefit; with AI adopted in days rather than years, capex spenders can observe how quickly new capacity is absorbed and size…

  3. Gaetano

    Alternative buyers absorb capacity if one anchor slows

  4. Brian Albrecht

    Obsolescence-driven hurdle rate offsets flatter demand

  5. Michael Spencer

    As BigTech companies build out massive hyperscale data centers to support generative AI, they lock in infrastructure advantages that create barriers to competition. Control over energy, computing resources, and supply chains allows winners to…

What would settle it

The dated tests.

Each test names the public source that settles it, the rule and the day. The Call’s number, the readers’ median and the machines’ numbers stand beside it, as on the Docket.

  1. CoreWeave, purchases of property and equipment as a share of revenue, quarter ended September 30, 2026: whether it comes in at or above 200%.

    On the Docket Pendingth037-t01Open question

    Specification pending

    The machinesClaude 63% · DeepSeek 78%

    Claude: 63%DeepSeek: 78%

    Your number

  2. CoreWeave, purchases of property and equipment as a share of revenue, quarter ended September 30, 2026: whether it comes in at or above 240%.

    On the Docket Pendingth037-t02Open question

    Specification pending

    The machinesClaude 55% · DeepSeek 60%

    Claude: 55%DeepSeek: 60%

    Your number

  3. CoreWeave, purchases of property and equipment as a share of revenue, quarter ended September 30, 2026: whether it comes in at or above 275%.

    On the Docket Pendingth037-t03Open question

    Specification pending

    The machinesClaude 22% · DeepSeek 32%

    Claude: 22%DeepSeek: 32%

    Your number

  4. Oracle, purchases of property and equipment as a share of revenue, quarter ended November 30, 2026: whether it comes in at or above 120%.

    On the Docket Pendingth037-t04Open question

    Specification pending

    The machinesClaude 38% · DeepSeek 60%

    Claude: 38%DeepSeek: 60%

    Your number

  5. Oracle, purchases of property and equipment as a share of revenue, quarter ended November 30, 2026: whether it comes in at or above 142%.

    On the Docket Pendingth037-t05Open question

    Specification pending

    The machinesClaude 12% · DeepSeek 30%

    Claude: 12%DeepSeek: 30%

    Your number

  6. Oracle, purchases of property and equipment as a share of revenue, quarter ended November 30, 2026: whether it comes in at or above 165%.

    On the Docket Pendingth037-t06Open question

    Specification pending

    The machinesClaude 7% · DeepSeek 12%

    Claude: 7%DeepSeek: 12%

    Your number

In The Buildout

The stories that take up this thesis, with their own Calls and tests.

A thesis page states one question and both sides of it; DeepStack takes no side in words, and its view is the number it gives each test before the date. Analysis and opinion, not investment advice. Voices are paraphrased from public writing and attributed by name; DeepStack shows no score, ranking or accuracy for any person. Pre-specified means the words were approved on or before the test’s date. Specified after the date means they were written afterwards: such a test is counted and shown, and never rated. An open question has no words yet. The Call’s number is the chance, from 0 to 100, that the Call gives the yes answer to a test’s question, recorded before the test’s date; it is DeepStack’s own reading, not a market price and not advice. The readers’ mark on the same line is the readers’ median, the middle of the numbers signed-in readers gave the test, shown from 25 readers. The machines: Each model read this page and nothing else. The number that counts is the latest one each model gave before the test closed.