Frontier AI Labs Are Renting Compute From Their Competitors
For technical teams, the real shift is not just who owns the GPUs, but how AI capacity is now assembled from contracts, leases, permits and power agreements. That changes deployment planning: workloads may look cloud-native at the service layer while being operationally dependent on a third partyโs site, utility feed, and financing timetable. Capacity planning therefore becomes a supply-chain problem as much as an architecture problem.
The architectural trade-off is flexibility versus control. Renting compute from a competitor or specialist operator can accelerate access to scarce infrastructure, but it also introduces exposure to termination windows, site readiness, and upstream usage conflicts. For platform engineers, that means model serving, training pipelines, and disaster recovery assumptions must be tested against the possibility that a provider reallocates capacity to its own business priorities.
From an enterprise integration perspective, the important question is whether workloads can move cleanly if one facility slips, a permit is delayed, or a contract changes. That implies stronger abstraction around data locality, checkpointing, network ingress, and backup recovery rather than assuming a single fixed region or vendor. The articleโs examples also suggest that โcontracted revenueโ is not the same as delivered service, so operations teams should distinguish commercial commitment from actual production readiness.
Procurement and risk teams should treat these arrangements as part of the technical design review. The useful checks are whether the provider can explain its upstream dependencies, whether exit and migration paths are operationally realistic, and whether the service depends on unapproved infrastructure. In this market, resiliency is no longer only about multi-region software; it also depends on the durability of the compute supply chain beneath it.
Anthropic reportedly proposed buying up to $10 billion in computing capacity from Meta over two years, and Meta was still weighing the offer as of July 17, 2026. Meta develops Llama and competes directly with Claude, yet it is considering becoming an infrastructure supplier to its rival.
Frontier labs are separating model development from infrastructure ownership. They are signing a mixture of public cloud contracts, dedicated compute agreements, long-term data center leases and custom facilities built by partners. That mixture does not eliminate construction, financing or permitting risk. It reallocates the risk across model developers, infrastructure operators, lenders and utilities, often through contracts whose most important protections are never disclosed.
How Anthropic Buys Its Capacity
Anthropic still runs substantial workloads on Amazon and Google Cloud, so nothing here replaces the public cloud. Three recently disclosed arrangements illustrate the shift.
The first is a dedicated compute agreement. Anthropic reportedly pays xAI $1.25 billion per month for the Colossus 1 facility in Memphis through May 2029, a figure disclosed in SpaceXโs May 2026 offering filing. Either party can terminate on 90 days’ notice, which cuts in both directions.
The second is a conventional real estate lease. TeraWulf Original Postress-releases/detail/142/terawulf-announces-anthropic-lease-at-justified-data-campus-and-sale-of-majority-interest-in-abernathy-joint-venture-to-fluidstack" target="_blank">announced on July 6, 2026 a 20-year agreement with Anthropic covering roughly 401 megawatts at a campus in Hawesville, Kentucky. The company told investors the lease should produce about $19 billion of contracted revenue and said it expects the arrangement to be supported by investment-grade credit. Initial capacity is due in the second half of 2027.
The third is the Meta proposal, which remains preliminary and may never be signed.
A fourth model sits alongside those three. On November 12, 2025 Anthropic committed $50 billion to custom-built United States infrastructure developed with Fluidstack in Texas and New York. The company said the facilities are built for its own workloads. That announcement did not specify the ownership, financing or land arrangements, so a dedicated facility should not be read as a directly owned one.
Who Carries The Building Risk
Oracle describes itself as the tenant of Project Jupiter in Doรฑa Ana County, New Mexico, a campus intended to support OpenAI workloads and authorized for as much as $165 billion in industrial revenue bonds. Authorization is not issued debt, and the amount actually raised has not been made public. The campus is waiting on an air quality permit. That proceeding is with the New Mexico Environment Department, a state agency, whose secretary ordered a public hearing after residents complained that their names appeared in supportive comments without their consent.
The Prompt: Get the weekโs biggest AI news on the buzziest companies and boldest breakthroughs, in your inbox.
On July 2, 2026, Oracle replaced its proposed gas-fired generation plan with a Bloom Energy fuel cell system and asked the department to approve the revised application. A lab can outsource the permitting work to an infrastructure partner, but it cannot outsource its dependence on the permit being granted and kept valid.
The spending behind that patience keeps climbing. Oracle reported capital expenditure of $55.7 billion in fiscal 2026, up from $21.2 billion the prior year. Chief financial officer Hilary Maxson guided to roughly $70 billion of Oracle’s own spending in fiscal 2027, with total outlays of $90 billion to $95 billion once customer-funded and reimbursable amounts are included.
The same conditions are producing suppliers nobody had heard of in 2024. Sharon AI, an Australian provider listed on Nasdaq, disclosed a $1.32 billion five-year cloud computing service agreement with an unnamed global AI lab on July 16, 2026. The company said the deal covers infrastructure in New Zealand, with revenue expected to begin in 2027. A contract of that size may help support project financing, although the company has not said the agreement alone finances the build.
The Undisclosed Provisions
Contracted revenue is a long way from delivered revenue. TeraWulf’s $19 billion arrives over 20 years and depends on capacity that does not yet exist, and Sharon AI’s first dollar lands in 2027.
The risk allocation is harder to read than the headline numbers suggest. Take-or-pay commitments, prepayments, minimum revenue guarantees, parent guarantees, termination payments and equipment ownership all move the exposure around, and none of these terms is public for every agreement. To the extent these projects are financed against long-term customer commitments, investors should examine whether tenant termination rights run shorter than the financing tenor.
Availability also depends on someone elseโs demand curve. SpaceXโs filing described the Colossus arrangement as a way to monetize unused compute capacity, and reporting has linked that spare capacity to weaker Grok usage. If xAI’s own compute demand rises, the economics underpinning the deal will change.
The Questions For Enterprise Buyers
In summary, the labs have not eliminated the construction problem. They have divided it among a larger set of counterparties, including bitcoin-mining operators, neoclouds, established cloud providers and, in a few cases, rival model companies.
Enterprises buying inference at scale should put three questions to any provider. The first is materiality, which means asking which facilities and upstream capacity providers actually serve the workload. The second is redundancy, which means asking what migration and backup provisions protect the service if either arrangement ends or a site is delayed. The third is regulatory dependence, which means asking whether any material facility is operating on a permit that has not yet been granted.
The compute market now rewards whoever can assemble power, chips, interconnection and regulatory approval fastest, and that ability sits outside the traditional hyperscalers more often than it did a year ago. For enterprises, developers, and operators now signing 20-year commitments, the market is becoming more fragmented, and its contractual dependencies are more consequential than the ownership question that gets the headlines.
Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.