The Short Answer
Between 25 and 31 August 2026, three things landed: Broadcom shipped private AI as a VMware feature, the EU classified ChatGPT by function under the DSA, and OpenAI published inference-silicon benchmarks against NVIDIA. Each weakens a different argument for renting AI infrastructure — technical, regulatory, economic. On ibl.ai you own all the code and the data, model-agnostic across any LLM, with no per-seat pricing.
Any one is a news item. The reason to read them together is that they move the same decision from three different directions.
What were the three signals?
Infrastructure. At VMware Explore on 31 August, Broadcom announced VMware AI Factory, the software-defined foundation of VMware Private AI Cloud: 150+ open-source models on a vLLM-based runtime inside VMware Cloud Foundation, a validated path on AMD Instinct MI350 GPUs with ROCm, zero-touch provisioning, and no per-token pricing. We covered it in private AI becoming a vSphere feature.
Regulation. On 31 August, the European Commission designated ChatGPT a Very Large Online Search Engine under the Digital Services Act — alongside Reddit and Roblox as Very Large Online Platforms — on the basis of what the service does, at roughly 159 million monthly EU users for its search function against a 45 million threshold. Four months to comply; penalties to 6% of global turnover. We covered it in the EU classifying ChatGPT by function.
Economics. At Hot Chips in late August, OpenAI published benchmarks for Jalapeño, its inference ASIC co-developed with Broadcom: 1.5–1.9x throughput per kilowatt and 1.7–3.6x lower end-to-end latency than NVIDIA's GB200 and GB300, at 700W against up to 1,400W. Set against inference costs falling roughly 95% in two years, we covered the consequence in per-seat AI being priced against a falling floor.
Why do these three belong in the same argument?
Because the case for renting AI infrastructure has always rested on three distinct claims, and each signal undercuts one.
| The argument for renting | What changed |
|---|---|
| "Running it ourselves is too hard" | Validated models now provision through tooling most enterprises already operate |
| "The vendor handles compliance" | Regulators classify by behaviour; you must evidence your own systems |
| "The API is cheaper than owning" | A fixed per-seat price does not follow a falling cost floor down |
The third row is the one that compounds. The other two are step changes; the cost floor keeps moving, and a contract signed against 2024 assumptions gets worse every quarter it runs.
What does this not mean?
It does not mean everyone should self-host, and the honest version of this argument has to say so.
A team of forty with modest, bursty usage should buy the API.
The break-even analyses that make self-hosting look compelling assume continuous load; hardware idle overnight has a far worse payback than a peak-throughput spreadsheet suggests. Own infrastructure only where the duty cycle justifies it.
It also does not mean VMware AI Factory is the answer. It relocates a dependency rather than removing one: off a model vendor's cloud, onto a hypervisor vendor's licensing and roadmap.
That may well be a trade worth making — most enterprise workloads already run there — but it is a trade, not an escape.
And none of this fixes model reliability. An agent that is confidently wrong with no internal signal is exactly as wrong on your own hardware.
What genuinely changed is narrower and more useful than "private AI won": the inputs to a build-versus-rent decision all moved in one direction inside a single week.
How should this change an evaluation you already did?
If you assessed this in 2024 or 2025 and concluded rent, the conclusion may still be right — but it was reached with different numbers.
Re-check three things specifically:
The technical assumption. If the objection was integration difficulty, price the same deployment against tooling your infrastructure team already runs, rather than against a from-scratch GPU cluster.
The compliance assumption. If the reasoning was that the vendor carries the regulatory burden, test it concretely: for a decision your AI made last month, can you produce the model, the data and the user's access context from records you hold?
The cost assumption. If the comparison was per-seat licensing against API pricing, redo it with current inference costs and with a realistic duty cycle — and ask which side of the contract captures the next 40% decline.
The layer worth owning is the one above the infrastructure: governance, identity, memory and model routing. Own that, and the hardware underneath stays a choice you can revisit. Rent it, and every improvement in any layer below arrives as someone else's margin.
Sources: European Commission — DSA designations · Broadcom — VMware AI Factory · OpenAI — Jalapeño inference chip