One campus. Several customers. Separate commitments.

Colocation has always sold one building to many tenants, and the arrival of AI has not changed that. In the Uptime Institute's 2025 survey, almost two thirds of colocation providers host hyperscale customers, who occupy a weighted average of 44 percent of those providers' space¹. What is new is what the AI tenant wants: contiguous, liquid-cooled, high-density blocks, delivered on committed dates, with power that already exists rather than power that has been applied for.

The hosting agreements now becoming public show the shape. TeraWulf's Lake Mariner campus in New York carries separate ten-year leases to Fluidstack, signed days apart in August 2025, for 200 MW and then a further 160 MW of critical IT load, each with its own Google credit backstop and its own delivery schedule²³. Cipher Mining's Barber Lake site in Texas hosts a separate 168 MW agreement on the same pattern⁴. One campus, one landlord, several distinct commitments.

A campus has one grid connection offer, one authorised import limit, a staged permission to energise and, beneath all of that, a reserved share of power for each customer. These are four different quantities and they are routinely confused. Utilities now report contracted pipelines far larger than anything that will be built: Dominion Energy put its data centre contracting pipeline at 47 GW in late 2025⁵. In Australia, the market operator commissioned separate analysis to distinguish credible data centre load from announced load before it would carry the figures into its planning scenarios⁶.

On a shared campus the discipline matters more, not less. Each customer's block is entitled to a defined share of the site's authorised capacity at a defined date. Adding the blocks together and comparing the total with the connection offer is how a campus ends up sold twice.

Spreading a campus across several customers can spread counterparty risk, although customers in the same market can still be hit by the same events. It also multiplies the number of delivery conditions in play. Each block has its own term, its own start date, its own price, its own acceptance conditions and its own consequences if it slips. Where a tenant's credit is not enough on its own, the enhancement attaches to the lease, not to the campus: Google's backstops at Lake Mariner and Barber Lake stand behind specific Fluidstack leases and their associated debt, not behind the landlord's other tenants²⁴.

The corollary for anyone lending to or insuring the campus is that a strong campus total never fixes one customer's shortfall. A campus that is ninety percent contracted to investment-grade counterparties and ten percent to a startup is two different credits sharing a substation. Each has to be underwritten, delivered and accepted on its own facts.

For the independent cloud, the shared campus is how growth actually happens. The first block is contracted, funded, built, energised and delivered. The second customer docks into the same connection, the same site works and the same operating team, and its block is funded against its own commitment. The connection offer that took years to secure is reused; the transformer that took two years to arrive serves the next block as well as the first⁷.

The capital picture shifts with it. Instead of one loan sized to one tenant, the campus becomes a set of separate commitments on one physical asset, each of which a lender can consider on its own terms once it is operating⁸. The operator keeps its cloud and its customers. The customers keep their own contracts. The lenders keep their own collateral.

Five things, in every block, on every campus. Scope: which racks, which capacity, which performance. Term: when payment starts and when it ends. Delivery requirements: what has to be true for that block to count as delivered, written before it is ordered. Power allocation: that block's share of the authorised limit at that date. And the result: whether what arrived for that customer matched what that customer agreed, independently checked and recorded so that every named organisation can read it and question it.

One build. Several customers. Separate commitments. One programme. CANUS puts each block together with the same partners, keeps each customer's requirements and result separate, and carries what still applies forward as the campus grows.