Build1 distinct publisher3 min readUpdated
The AI memory buildout is now setting the price of ordinary servers. OVHcloud is passing on part of a 6x input move, and its purchasing runs month to month while Amazon's does not.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
Start with the pass-through. The steepest increase in the catalog, 87 percent on 2026-edition gaming servers [6], is a price multiple of 1.87. Memory, on OVHcloud's own purchasing index, sits at 604 against June 2025, or 6.04x [3]. The first is about 31 percent of the second [1]. Memory is one line on a bill that also carries chassis, CPUs, drives and network cards, so this is not a clean cost-recovery sum, and the 15 to 20 percent rises on CPUs, motherboards and network cards that Klaba says he has been told to expect are not in the June index at all [5]. Even so, the worst-treated customer in the catalog is being asked for less than a third of the input move, and the untouched ranges, Kimsufi and Rise among them, are being asked for nothing [7].
The steps matter more than the level. Going from 6x to 9x between June and September is a further 50 percent in three months [2]; 9x to 12x by early 2027 is another 33 percent on top of that [3]. September's prices are being set against a figure Klaba says he already knows [4], and the early-2027 figure is in no published price list yet. That is what the Reddit complaint was actually about. The commenter bammitscamm objected to the timing, not the arithmetic, because April had only just happened [17], and two increases inside six months [18] make the next one a scheduling question rather than a surprise.
Amazon buys memory in the same market and has repriced one product. EC2 Capacity Blocks for ML rose roughly 20 percent in July after about 15 percent in January, which compounds to around 38 percent across the year [4], while the rest of the catalog, Trainium instances included, did not move, and the change appeared on the pricing page without announcement [13]. The gap is procurement, not engineering. Hyperscalers contract years ahead in volumes that earn priority allocation, and several design their own accelerators [14], whereas OVHcloud, by Klaba's own description, orders month by month over 12 months with no guaranteed purchase price and no firm read on customer demand [12]. His stated worry is supply rather than margin: running out of parts and being unable to deliver [11].
The saving plan change is where a customer has to decide something. The one-month, six-month and 24-month plans go away, leaving 12 and 36 months, each locking price for its term [9]. Klaba puts the end of the exceptional period at 2028 [10]. A 12-month lock signed this autumn expires in autumn 2027, inside that window; a 36-month lock runs to autumn 2029, past the far end of his own forecast [5].
The Gen3 unbundling on October 1, with storage at EUR 0.000146 per GB per hour and IP addresses at EUR 0.0027 per hour [8], is a separate move and reads as one: costs that used to sit inside the instance price now track usage. The planning consequence of all of it is not a percentage. Unit costs for ordinary compute are being restated in multiples, which means a 2027 budget built on 2025 memory prices is wrong by a factor, not by a few points.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Indexed to June 2025, OVHcloud's own purchasing figures put memory at 604 by June 2026, SSDs at 323 and hard drives at 148.
Klaba adds that NVMe drives are at 7x and hard drives at 3.5x, and reports hearing that CPUs, motherboards and network cards will rise 15 to 20 percent.
Renters of 2026-edition gaming servers face the steepest rise at 87 percent, while other recent servers go up 40 to 59 percent, all from September.
OVHcloud is dropping its one-month, six-month and 24-month saving plans, keeping the 12- and 36-month options, which lock pricing for their duration.
Hyperscalers contract for memory years ahead in volumes that earn priority allocation, and several design their own accelerators; a provider buying merchant components on rolling monthly orders has neither cushion.
Reddit commenter bammitscamm summarized the schedule and added: "Not happy about this, especially after just raising the prices in April."
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Specific vendor primary data, no independent corroboration
The pricing actions are unusually concrete for a single-source story: named ranges, percentage increases, effective dates, unit prices for unbundled Gen3 storage and IPs, and an indexed purchasing chart published by OVHcloud itself, plus an observable AWS pricing-page change. What is missing is any independent measurement — no DRAM/NAND market index, supplier disclosure or analyst data validates the 6x claim, quotes are platform translations of French X posts, the CPU/motherboard/NIC figures are explicitly hearsay, and the whole cluster rests on one publisher.
Committed, dated price changes already in force across a catalog
These are not announcements of intent: increases take effect in September, line-item unbundling on October 1, saving plan terms are being withdrawn, and an April increase already happened — so the repricing is being applied to a live customer base at scale. Adoption evidence on the customer side is much thinner: the article itself calls the Reddit reaction limited, with one named commenter and one report of moving to self-hosted hardware, and no data on how many customers sit on repriced versus shielded generations.
Reporting restrained; vendor's duration and escalation framing outruns its evidence
The article is disciplined where it can be measured — it notes the 87 percent rise passes through only about a third of the 6.04x input move, flags the translation caveat and hearsay figures, and closes by observing memory markets are cyclical. The overstatement sits in the sourced vendor framing that the reporting carries forward: a fixed 'exceptional until 2028' horizon, 9x and 12x forecasts with no market data behind them, and an unnamed MSP's expectation of imminent Azure and AWS increases when the only observed hyperscaler move is a reserved GPU product. That tilts modestly positive rather than sharply.
Interested parties on every load-bearing claim
The core evidence originates with the vendor doing the repricing: OVHcloud benefits from attributing increases to external fab decisions, from publishing its own cost index, and from asserting it remains the cheapest bare-metal and public cloud option even at 2x rather than 3x cheaper. The framing that competitors will soon follow serves the same interest and comes from a managed service provider founder who resells such capacity, while the sovereignty-dependency argument is voiced by a commentator serializing a book on digital sovereignty. Amazon's near-silence is itself commercially motivated. The article discloses these positions rather than concealing them.
Facts firm, causal and forward layers soft, one publisher
High confidence attaches to the announced changes themselves — dates, percentages and unit prices are specific and would be quickly contradicted if wrong — and to Amazon's observable pricing behaviour. Confidence drops on everything explanatory or forward-looking: the HBM reallocation mechanism, hyperscaler contracting practice, the 9x/12x path and the 2028 horizon are all single-sourced, partly translated and in places explicitly second-hand, and the supplied source body is truncated before its conclusion.
invest
Microsoft's Idle AI Chips Are A Construction Problem, Not A Shortage1 distinct publisher
product
AWS quarantines leaked keys. Truffle Security's sweep says 9,342 of them still work.1 distinct publisher
build
Identical Helm charts, three clouds, one OOMKill loop: portability is a claim about YAML1 distinct publisher
invest
Amazon puts the memory crunch on the shelf: Echo Dot up 60%, Kindle up $401 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 23, 2026