The Number That Signals Real Demand

On June 11, 2025, Oracle released its financial results for the final quarter of fiscal 2025. Most investors focus on earnings per share — the company's profit divided by the number of shares outstanding. But there's a different number hiding in the results that tells a more important story: the backlog.

Oracle calls this Total Remaining Performance Obligations, or RPO — the money customers have already committed to pay for services Oracle hasn't yet delivered. Think of it as signed contracts waiting to be fulfilled. Oracle's RPO hit $138 billion in Q4, up 41% from a year earlier, when it was $98 billion. Two years ago, it was roughly $68 billion. In just twenty-four months, Oracle's contracted backlog has doubled.

For anyone trying to understand whether Oracle's cloud business is growing or slowing, this backlog number is the real story. Earnings-per-share figures — $1.19 on a strict accounting basis (GAAP), or $1.70 using the company's preferred adjustments — ticked up modestly. That alone might look unimpressive. The backlog tells you something much bigger is happening.

Where Oracle's Cloud Growth Is Coming From

Oracle's cloud business is splitting into two high-growth channels, each addressing a different customer problem.

The first is Cloud@Customer, which places Oracle's infrastructure inside a customer's own data center or government facility. Revenue from this product more than doubled year-over-year — that's 104% growth, which is remarkable for a company Oracle's size. Regulated industries — banks, healthcare providers, defence contractors — are driving this demand. They have legal or security rules that keep sensitive data from leaving their own property, and renting space on someone else's cloud doesn't always satisfy those requirements. Cloud@Customer solves that problem.

The second channel is MultiCloud. This targets customers already heavily invested in AWS, Microsoft Azure, or Google Cloud who want to use Oracle's database technology without ripping out their existing infrastructure. Oracle has signed formal partnership agreements with all three of the big cloud providers, and those deals are translating into substantial signed bookings. The company expects this channel to keep growing at triple-digit rates into fiscal 2026.

Together, these two products cover most enterprise procurement scenarios. Some customers can't move workloads off-premise — that's Cloud@Customer. Others are already locked into a hyperscaler ecosystem — that's MultiCloud. The fact that Oracle is winning in both markets at once is why the backlog has expanded so dramatically.

How to Read RPO: Contracts, Not Cash

Here's what RPO actually represents. When Oracle signs a multi-year cloud contract — typically three to five years with minimum spending commitments — it doesn't recognize the entire amount as revenue immediately. Instead, it recognizes revenue as it delivers the service, month by month or quarter by quarter. The difference between what customers have committed to pay and what Oracle has already recognized as revenue shows up as RPO.

RPO is not revenue. It's not cash. It's a contractual obligation, and like all contracts, it carries risks: customers might ask for amendments, performance might slip, or broader economic conditions could change the game. But it is a genuine claim on future money. And $138 billion growing 41% year-over-year is not a figure you can dismiss. It means Oracle has materially more contracted work in front of it than it did a year ago, concentrated precisely in infrastructure — the most capital-intensive, highest-margin part of the cloud business.

The comparison to AWS is instructive here. When Amazon Web Services was in its growth phase between 2017 and 2020, its backlog consistently grew faster than its reported revenue. That pattern preceded years of substantial revenue acceleration. Oracle is not AWS — it doesn't have AWS's breadth of services or developer ecosystem — but the backlog mechanics are similar. Large contracted obligations growing at this pace set a floor on how much revenue will be recognized in the coming years, regardless of whether Oracle lands new deals or not.

Why the Earnings Number Looks Modest

The earnings-per-share figures ($1.19 GAAP, $1.70non-GAAP) grew only slightly from a year earlier ($1.11 GAAP, $1.63 non-GAAP). That gap of roughly 51 cents reflects standard accounting adjustments: stock-based compensation paid to employees, and the amortization of intangibles from Oracle's $28 billion acquisition of the healthcare software company Cerner back in 2022. These adjustments are normal across the software and cloud industry, and Oracle's gap hasn't widened materially, which means the company isn't hiding deteriorating profitability beneath rosy non-GAAP adjustments.

The real question is why earnings growth doesn't match backlog growth. The answer is likely this: Oracle is in heavy investment mode. Building data centers, procuring hardware, installing power systems, and hiring engineers to manage the infrastructure is expensive. That spending reduces reported profit in the short term, even as signed contracts pile up. Whether that investment eventually translates into stronger profits in 2026 and 2027 remains to be seen.

What Could Go Wrong in 2026

Oracle has guided for continued triple-digit MultiCloud growth into fiscal 2026. That's a forward-looking statement, and it's worth being skeptical about any forecast, particularly in fast-moving markets. Several things could slow execution: partnerships with hyperscalers could encounter friction, enterprise IT budgets might tighten, or capital might get diverted toward AI infrastructure investments elsewhere. Macro conditions could also cool appetites for multi-year commitments.

But there's one thing that's not speculation: the $138 billion backlog already exists. Customers have signed contracts. The question for 2026 is not whether Oracle has demand. The demand is contractually locked in. The harder question is whether Oracle can deliver — whether data centers get built on time, whether hardware arrives as planned, and whether the company can convert its contracted obligations into recognized revenue on schedule. That's an operational problem, not a sales problem. And it's the crucial test for what comes next.

For anyone tracking whether Oracle's cloud business is firing on all cylinders, the backlog is your anchor. The current portion of RPO — what will be recognized as revenue within the next twelve months — is the most immediate revenue visibility metric. Fiscal 2025 established that enterprise cloud demand is not decelerating. Fiscal 2026 will reveal whether Oracle can build fast enough to meet it.