Summary

  • OVHcloud spent €238.5 million on capital expenditure excluding acquisitions in the first half of FY2026, equal to 42.9% of €555.3 million in revenue.
  • The company said growth capex included around 11% voluntarily pulled forward from the second half. Read against H1 revenue, that is roughly €61 million, but it is not a company-reported euro bridge.
  • A separate €50 million stock of memory and disks is reserved exclusively for FY2027 and sits outside the 33–35% adjusted-capex guidance.
  • Components and work in progress rose by €75.4 million on a net book basis, while higher commissioned-server volumes were already lifting depreciation. Cash, service readiness and revenue are therefore not interchangeable measures.

The ratio that arrives before the service

A cloud provider can spend money long before a customer can buy what the money is meant to create. It orders memory and disks, assembles servers, fits out technical space, connects equipment, tests it, commissions it and only then exposes a product that somebody may use. The cash-flow statement sees the purchase near the beginning. Depreciation starts around commissioning. Revenue waits for deployment and demand.

That sequence matters when reading OVHcloud's first-half FY2026 figures. Revenue was €555.3 million, up 5.5% like for like. Capital expenditure excluding acquisitions was €238.5 million, up from €193 million a year earlier. The ratio rose from 36.0% to 42.9%. Put those figures side by side and it is easy to tell a blunt story: investment is running much faster than sales.

It is also an incomplete story. OVHcloud explicitly said it had brought hardware spending forward to secure supplies and reduce exposure to exceptional inflation in memory components and disks. Part of the first-half cash outflow therefore belongs economically to a later operating period. The ratio records when equipment was bought, not when all of it became a saleable service.

What sits inside 42.9%

OVHcloud divides capital expenditure into recurring and growth buckets. Recurring capex is the spending on servers and related infrastructure needed to replace revenue from machines that are downgraded, taken offline or refurbished. Growth capex is everything else required to support revenue growth.

In H1, recurring capex was €72 million, or 13.0% of revenue. Growth capex was €166 million, or 29.9%. The company said around 11% was voluntarily front-loaded for H2 FY2026. If that percentage is applied to the €555.3 million H1 revenue base, it is about €61 million. That calculation is useful for scale, but it must remain labelled as an editorial derivation: OVHcloud did not publish a cash bridge saying that exactly €61 million should be removed from the half-year figure.

Even with that caution, the message is clear. A material portion of the 42.9% ratio was about procurement timing. A lower ratio in H2 could simply be the mirror image of the pull-forward rather than evidence that management had curtailed expansion. Conversely, the high H1 number does not establish that an equivalent amount of productive capacity was already online.

There is another timing layer. OVHcloud plans to build a stock of roughly €50 million in memory and disks solely for FY2027. It says these components are not at risk of obsolescence, that the purchase should secure availability and freeze prices, and that dedicated exceptional financing will cover it. The stock is excluded from the FY2026 adjusted-capex target of 33–35% of revenue. It still matters to the economics. The company is committing finance today to protect a future production schedule, even though the headline guidance has been designed to keep that stock outside its perimeter.

The waiting room on the balance sheet

The balance sheet offers a partial view of the gap between buying and commissioning. The net book value of components and work in progress was €242.8 million at 28 February 2026, up from €167.4 million at the August year-end. That €75.4 million increase is not a direct map of front-loaded H2 hardware: the line contains both components and work in progress, and its movements include more than one type of investment. But it is evidence that a larger pool of value remained between purchase and fully commissioned productive assets at the reporting date.

At the same time, some equipment had already crossed that boundary. OVHcloud reported €131.4 million of depreciation and impairment on property, plant and equipment in H1, versus €120.1 million a year earlier. It attributed the movement mainly to an increase in the production volume of commissioned servers. Total depreciation, amortisation and impairment reached €185.6 million.

Those two disclosures can coexist without contradiction. More servers can enter service while an even larger amount of components and unfinished equipment accumulates for later use. The useful market question is not whether capex is “high” or “low”. It is how quickly value moves from cash outflow to work in progress, from work in progress to commissioned servers, and from commissioned servers to revenue-bearing utilisation.

Revenue has its own clock

OVHcloud's Q3 update shows that demand did not stand still. Quarterly revenue was €289.6 million, up 6.9% like for like. Public Cloud generated €65.6 million and grew 20.2% like for like. The company kept its FY2026 guidance for 5–7% organic revenue growth, an adjusted EBITDA margin above FY2025, adjusted capex of 33–35% of revenue excluding the FY2027 stock, and positive levered free cash flow.

That is encouraging evidence of commercial acceleration, particularly in Public Cloud. It is not a utilisation report for the H1 purchases. OVHcloud does not disclose, in these documents, a bridge from a euro spent on a component to a server commissioned, a unit of sellable capacity and then a euro of revenue. Readers should resist manufacturing one from adjacent numbers.

The distinction is especially important for a vertically integrated operator. OVHcloud designs and assembles its own servers and manages data centres and network infrastructure. That control can shorten some supply-chain dependencies and make purchase timing a strategic lever. It also makes the reported investment cycle an amalgam of component buying, production and facility work. A single capex-to-revenue ratio compresses all of those stages into one percentage.

Cash discipline after the pull-forward

OVHcloud generated €32.3 million of unlevered free cash flow in H1. Net debt excluding lease liabilities was €1.125 billion at 28 February, compared with €1.103 billion at the August year-end. Management says it can retain positive levered free cash flow for FY2026 despite the higher capex range and separately financed FY2027 inventory.

This is the part of the thesis that has not yet been proved. Pulling purchases forward can create real savings: OVHcloud estimates about €10 million from securing most requirements before further price rises. Yet it also consumes financing capacity earlier and leaves execution risk between purchased component and paid service. If demand, commissioning or product deployment slips, the saving on unit cost can coexist with a slower return on capital.

The full-year result, scheduled for 20 October 2026, should show whether the H1 surge really was a timing bulge. Until then, the best interpretation is neither “overbuilding” nor “capacity triumph”. It is that OVHcloud has chosen to insure its hardware pipeline against price and availability risk, accepting a larger first-half asset and cash commitment in exchange.

Sources