Oracle's $70B AI buildout runs on new debt and one customer
Roughly $40 billion in fresh capital against a $455 billion backlog that is reportedly two thirds tied to OpenAI.
Roughly $40 billion in fresh capital against a $455 billion backlog that is reportedly two thirds tied to OpenAI.
Oracle is committing roughly $70 billion in net capital expenditure for fiscal 2027, more than triple what it spent just two years ago, and the cash is not coming from operations. It is coming from capital markets: about $40 billion in new debt and equity, layered on top of the $18 billion Oracle already raised in debt over the prior year, against a $455 billion remaining performance obligations backlog that is reportedly two-thirds tied to a single customer, OpenAI. The question the market is now pricing is not whether Oracle can build the datacenters, but whether the financing structure holding the thesis together is resilient if that one customer's compute demand cools.
The numbers, drawn from Oracle's fiscal Q4 2026 results reported by The Register, are stark on their own. Quarterly revenue rose 21% year over year to $19.2 billion. Full-year capital expenditure for fiscal 2026 reached $55.7 billion, up from $21.2 billion the year before (The Register, "Oracle's AI datacenter splurge gives investors the capex jitters"). The forward plan steps the pace up again: net capex of roughly $70 billion in fiscal 2027, funded by approximately $40 billion in new debt and equity, including a $20 billion equity issuance Oracle has already announced.
Chief Financial Officer Hilary Maxson, presenting the fiscal 2027 plan, said Oracle does not anticipate additional debt funding in calendar year 2026, framing the announced raise as the full envelope (The Register coverage of Oracle's Q4 results). The pitch from Oracle's leadership, including Magouyrk on capex drivers, is that component pricing and delivery timing are driving the step-up, not a fundamental re-rating of the buildout. In Oracle's framing, the capex jump is a procurement story, not a demand story.
That framing is the part the market is testing. When a company funds a multi-year infrastructure build with new debt on revenue contracted largely from one counterparty, the load-bearing question is not the headline capex number but the math behind it. Oracle's $455 billion remaining performance obligations figure is the contractually committed backlog. The Register reports that roughly $300 billion of that is tied to OpenAI, a concentration fact rather than a confirmed Oracle disclosure. If the reported figure is in the right neighborhood, OpenAI is effectively the single asset against which Oracle is issuing a meaningful share of its new debt and equity.
Three conditions would break the math. The first is OpenAI pulling back compute commitments as its own revenue ramp or model economics shift. The second is a tightening in credit conditions that raises the cost of the remaining debt Oracle still has to raise. The third is a slip in the procurement-driven component-cost story, which would push capex above the $70 billion line and force another funding round on less favorable terms. None of these are predictions. They are the conditions under which the structure stops working.
What to watch next is concrete. Oracle's next 10-Q will show how the $20 billion equity tranche lands, who took it, and at what discount. The 10-K should break out customer concentration in the RPO disclosure, or conspicuously fail to. Credit default swap pricing and the spread on Oracle's upcoming bond issuance will tell you what debt investors actually think of the structure, separately from what equity investors say on the call. And OpenAI's own funding announcements, including any compute commitments to other clouds, will be a real-time read on whether the $300 billion figure is the floor or the ceiling on Oracle's exposure.
The interesting question is not whether Oracle can pour concrete. It is whether a financing template built on one customer's demand and one cycle's credit conditions can survive both shifting at once.