The Numbers That Matter

Oracle reported its fiscal fourth-quarter and full-year 2025 results on June 11, 2025, and the headline that deserves the most attention is not the earnings-per-share figure — it is the backlog. Total Remaining Performance Obligations (RPO) — the contracted revenue not yet recognized, a forward-looking proxy for demand — expanded 41% year-over-year to $138 billion in Q4 FY25.

For context, a year earlier Oracle's RPO stood at $98 billion, itself a 44% jump on the prior comparable period. In two years the figure has gone from roughly $68 billion to $138 billion. That is a doubling of contracted backlog in twenty-four months, and it is the single most consequential data point in the release for anyone trying to assess Oracle's trajectory in enterprise cloud infrastructure.

GAAP EPS for Q4 FY25 came in at $1.19, with non-GAAP EPS at $1.70, per the company's investor release. A year prior, Q4 FY24 GAAP EPS was $1.11 and non-GAAP EPS was $1.63 — so the per-share earnings progression is steady but unspectacular on its own. The gap between the two EPS figures — roughly 43 cents in both periods — reflects the standard non-GAAP adjustments for stock-based compensation and amortisation of intangibles, the usual levers Oracle and its peers pull to present an operating picture stripped of acquisition accounting noise.

Cloud@Customer and MultiCloud: Where the Growth Is Originating

The structural story inside FY25 is the acceleration of Oracle Cloud@Customer — the sovereign and dedicated cloud deployment model that plants Oracle's infrastructure physically inside a customer's own datacentre or government facility. Revenue from Cloud@Customer grew 104% year-over-year across the full fiscal year. Triple-digit growth on a now-material revenue base is unusual at Oracle's scale, and it signals that regulated industries — financial services, healthcare, defence — are committing serious capital to on-premise cloud models that satisfy data residency and security requirements that public hyperscaler deployments cannot always meet.

Oracle has also flagged that it expects MultiCloud revenue to continue growing at triple-digit rates into FY26. MultiCloud, in Oracle's framing, refers to deployments where Oracle Database and its cloud services run natively within the infrastructure environments of other major cloud providers — principally AWS, Microsoft Azure, and Google Cloud. The company has formalised interconnect agreements with all three, and those partnerships are evidently translating into contracted bookings that are feeding the RPO line.

The convergence of Cloud@Customer and MultiCloud as simultaneous growth vectors is worth unpacking. Cloud@Customer addresses the customer who cannot move workloads off-premise. MultiCloud addresses the customer who is already deep in a hyperscaler's ecosystem and wants Oracle's database technology without migrating. Together they cover a wide arc of enterprise procurement postures — which is one reason the backlog is expanding at rates that most mature enterprise software companies cannot sustain.

RPO as a Leading Indicator: What the $138 Billion Means Operationally

RPO mechanics are worth being precise about. Under ASC 606, RPO captures the aggregate transaction price allocated to performance obligations that are unsatisfied or partially unsatisfied at period end. It is not revenue — it is a contractual claim on future revenue, subject to execution risk, contract amendments, and the usual lumpy recognition patterns of multi-year infrastructure deals. Long-duration cloud infrastructure contracts, often spanning three to five years with committed consumption minimums, will inflate RPO relative to shorter-term SaaS arrangements.

That caveat noted, 41% year-over-year growth to $138 billion is not a figure you can handwave away. It means Oracle has materially more contracted work in front of it than it did twelve months ago, and the acceleration is occurring precisely in the infrastructure segment — OCI, Cloud@Customer, database as a service — where capital intensity is highest and customer switching costs, once infrastructure is embedded, are substantial.

The pattern here is familiar to anyone who tracked AWS's trajectory in the 2017–2020 period, when backlog growth consistently outran reported revenue growth by a wide margin, prefiguring the revenue step-changes that followed. Oracle is not AWS — its developer ecosystem and breadth of services are not comparable — but the RPO dynamic rhymes. Contracted obligations at this scale, growing at this rate, set a floor under near-term revenue growth that organic deal flow alone could not.

Earnings Quality and the Non-GAAP Gap

The $0.51 spread between GAAP ($1.19) and non-GAAP ($1.70) EPS in Q4 FY25 is consistent with prior periods and primarily reflects amortisation of intangibles from the $28 billion Cerner acquisition closed in June 2022, ongoing stock-based compensation, and acquisition-related charges. The stability of this gap across quarters is itself informative: it means Oracle's non-GAAP adjustments are not materially expanding, which rules out aggressive earnings management through add-back inflation. Cash EPS and free cash flow per share remain the cleaner metrics for stress-testing valuation, and Oracle has not provided those in the headline release in a way that would change the structural read.

The FY26 Forward Posture

Oracle's guidance language around FY26 MultiCloud growth — specifically the expectation of continued triple-digit percentage expansion — is forward-looking and carries the standard suite of execution risks: hyperscaler partnership continuity, enterprise IT budget cycles, AI infrastructure spending competing for the same capital pools, and macroeconomic pressure on multi-year commitment appetite. None of those risks is trivial.

What is less uncertain is the demand signal embedded in the $138 billion RPO. That figure is not a forecast — it is a contractual stock. The question for FY26 is not whether Oracle has the demand; the contracts exist. The question is whether capacity — data centre construction, hardware procurement, power provisioning — can keep pace with the obligation to deliver. Oracle has been building aggressively, and Cloud@Customer's on-premise model partially offloads the capacity burden to customers. But converting backlog to recognised revenue on schedule is an operational execution challenge that the RPO number itself cannot resolve.

The year-over-year EPS progression — GAAP up from $1.11 to $1.19, non-GAAP up from $1.63 to $1.70 — is modest relative to the RPO expansion rate. That divergence is consistent with a company in a heavy investment phase, absorbing capex and hiring costs to build the infrastructure capacity the backlog demands. Whether that investment cycle translates into meaningful operating leverage in FY26 and FY27 is the core analytical question the results leave open.

For practitioners modelling Oracle's revenue trajectory, the $138 billion RPO — split between current and non-current portions, which Oracle discloses separately — is the anchor. The current RPO portion, representing obligations expected to be recognised within twelve months, is the more immediate revenue visibility metric. The full-year and Q4 FY25 results establish that Oracle's enterprise cloud demand pipeline is not decelerating. The execution story is what FY26 will write.