Oracle's Real Growth Story: Why the Backlog Number Matters More Than Earnings

On June 11, 2025, Oracle announced its latest quarterly results. Most investors focus on earnings-per-share — how much profit the company made per share of stock. But there is a less famous number in the release that actually tells you more about Oracle's future: the backlog.

Oracle calls it Total Remaining Performance Obligations (RPO). In plain terms, it is the money Oracle has already promised to deliver services for, but hasn't recognised as revenue yet. Think of it like a pizza restaurant with advance orders booked for the next three months — the cash is committed, but the pizzas haven't been made yet.

Oracle's RPO hit $138 billion at the end of its fiscal year 2025. A year earlier it was $98 billion. Two years ago it was roughly $68 billion. According to the company's investor release, the backlog has roughly doubled in two years. For a company Oracle's size, that kind of growth in committed future work is unusual and significant.

The Earnings Numbers Are Steady, Not Dramatic

Oracle's reported earnings per share for the quarter came to $1.19 on a standard accounting basis, or $1.70 if you exclude certain costs. A year earlier those figures were $1.11 and $1.63. The difference between the two numbers — about 43 cents — comes from adjusting for stock-based compensation and other acquisition-related charges. This is standard stuff that most large companies do, and it is not a sign of anything unusual.

The modest increase in per-share earnings is worth comparing to the 41% jump in the backlog. That gap tells a story worth understanding: Oracle is investing heavily in building out the infrastructure to deliver on all those future commitments. Big spending now, bigger profits later — if execution goes according to plan.

Two Strategies Driving the Growth

Inside these numbers, two specific business lines are growing fast.

Cloud@Customer is Oracle's name for dedicated cloud computing that runs inside a customer's own data centre or government facility. This matters because some industries — financial services, healthcare, defence — have strict rules about where their data can live. They cannot put everything on public cloud providers like Amazon or Microsoft. Cloud@Customer grew 104% year-over-year across the full fiscal year. Triple-digit growth at Oracle's scale is rare.

MultiCloud refers to Oracle's database and cloud services running on top of other companies' infrastructure — Amazon Web Services, Microsoft Azure, and Google Cloud. Instead of forcing customers to choose, Oracle lets them use its technology wherever they already work. The company has formal partnerships with all three cloud giants, and these are feeding into the backlog.

The two strategies cover a lot of ground. Cloud@Customer grabs customers who cannot move their data off-site. MultiCloud grabs customers already deep in another company's ecosystem. Together, they explain why the backlog is expanding so rapidly.

What a $138 Billion Backlog Actually Means

The $138 billion is not revenue yet. It is a contractual promise. The rules of accounting (called ASC 606, if you need the jargon) define it as the price of work Oracle has signed up to do but hasn't finished. Most of these are long-term infrastructure deals — three to five years — with minimum spending commitments built in.

That matters because it is not speculative. The money is committed in contracts. Oracle has materially more work guaranteed to do over the next one to two years than it did a year ago. That work is also in the highest-leverage part of Oracle's business — cloud infrastructure — where once a customer's systems are embedded, switching to someone else gets expensive.

The parallel here is worth noting. Amazon Web Services grew its backlog dramatically in the 2017–2020 period, and that backlog consistently expanded faster than reported revenue. When Amazon finally started recognising all that committed work as revenue, the growth numbers jumped. Oracle's pattern rhymes with that story, though Oracle is smaller and has less market dominance than AWS does.

The Investment Burden Ahead

If Oracle has doubled its backlog in two years, where is all the extra profit? The answer is that Oracle is spending heavily right now to build the data centres and systems needed to deliver on all these contracts. Think of it as borrowing against the future: heavy spending today, heavier profits later — assuming the infrastructure gets built on time and on budget.

This is a realistic concern. Converting a $138 billion backlog into revenue on schedule is not automatic. It requires building data centres, buying hardware, and securing power supply. Oracle says it is investing aggressively, and the Cloud@Customer model helps by letting customers build some of the infrastructure themselves. But execution risk is real.

What Matters Going Forward

Oracle has said it expects MultiCloud revenue to keep growing at triple-digit rates into next fiscal year. That is a strong signal about demand. But demand alone is not enough — you have to be able to deliver.

The core question for the next year or two is whether Oracle can turn all those backlog contracts into actual revenue while staying on budget. The backlog number tells you demand is there. Whether Oracle has the operational discipline and capital to meet that demand — that is what will determine whether these results look like the start of a meaningful growth story, or a company that overcommitted and struggled to catch up.

The RPO number is the anchor for anyone trying to understand where Oracle goes next. It is not a forecast or a hope — it is money already promised. What matters now is execution.