What lenders underwrite on a GPU cluster

An equipment invoice documents cost, not the cash available for debt service or the proceeds from a distressed sale. Recovery depends on the model, age, condition, location, access rights and market at the time of sale.

Two clusters with identical hardware can therefore support different structures. One may have a committed customer with a defined payment floor; another may rely on future sales. Both may be financeable, but a lender will size and price the risks differently.

Review the customer contract and equipment schedule together. The equipment list tells the lender what may be delivered and pledged; the contract says when, and under which conditions, the deployment can produce cash.

A lender tests whether demand is contracted, when it starts and who owes the payment.

Tenor against the asset. A contract shorter than the repayment period leaves a renewal or remarketing gap. The tenor mismatch page examines who carries it.

Who pays. A strong payer on a firm capacity commitment supports a different credit case from a weaker payer with broad termination rights.

What is owed. A committed minimum can support predictable receipts, subject to performance and termination terms. Usage pricing without a minimum makes receipts depend on future consumption. A framework agreement may allow orders without requiring them.

Concentration. Where one customer supplies most receipts, its credit and its ability to exit matter throughout the debt term.

Compute is the only layer of the stack that can be physically moved, which makes it easy to underrate how tightly it is bound to its site.

A cluster generates revenue only while it is powered, cooled and connected. So the hosting position is part of the credit whether or not anyone has documented it that way:

• Power. Contracted, at adequate capacity, for at least as long as the compute contract runs. Power that expires first converts a performing asset into a relocation problem.
• The hosting or colocation agreement. Its term, its termination rights, and what happens to the equipment on termination. An agreement that allows the host to deny access on dispute is a serious impairment, because access is the precondition for every remedy.
• Cooling and density. Rack-scale systems are not deployable into arbitrary space. A facility that cannot cool the configuration is a constraint on the asset, not a detail of the fit-out.
• Who owns what. Where the equipment owner, the facility owner and the operator are different parties, the boundaries have to be written down before anyone advances capital against any of it.

Site quality is a financing input, which is why the site qualification questions belong in the same conversation.

Recovery analysis asks a narrow question: if this stops performing, what is realistically obtained, how quickly, and at what cost.

Three things make that harder for compute than for the rest of the stack.

The value moves fast. Accelerator values track the product cycle rather than a depreciation schedule, and the decline is neither smooth nor predictable. The residual value page covers how the curve behaves and why it drives structure.

The asset is movable. That sounds like a benefit and is mostly a complication — movable equipment can be relocated, commingled, or disputed, and securing it properly is its own discipline. See collateralizing compute.

Distress is correlated. The circumstances in which one party needs to sell a cluster are usually the circumstances in which several do. Recovery assumptions drawn from a strong market do not survive the market in which they would be tested.

None of this makes compute unfinanceable. It makes recovery a weak second line of defence, which is precisely why the contract carries the underwriting.

The difference between a transaction that progresses and one that stalls is usually preparation rather than merit. A package that can be reviewed rather than assembled contains:

• The compute contract, with tenor, committed volumes, pricing mechanics and termination rights visible rather than summarised.
• Counterparty information sufficient to form a credit view, and an honest statement where that information is thin.
• The hosting position — facility, term, power, cooling, access rights, and what happens on termination.
• The equipment schedule, with configuration, delivery timing and current status. Ordered, delivered and deployed are three different states and should not be presented as one.
• The ownership structure — which entity holds the equipment, which holds the contract, and what else sits in each.
• The operating assumptions, particularly utilisation and power cost, stated as assumptions rather than as facts.

Assembling this in advance is not presentation. It is the difference between asking capital to underwrite an asset and asking it to fund the discovery of what the asset is.

The funding gap appears before a customer starts paying. A sponsor may owe equipment deposits and site costs while financing is still being arranged. IREN's 2026 annual report lists cash, equity, convertible notes, GPU financing and customer prepayments among its funding sources; it also says some equipment orders and site work may precede the related financing or customer contract. (IREN FY2026 Form 10-K, as of October 19, 2026) That is a disclosed example of timing risk, not a required order for every transaction.

Build a tranche schedule for each cluster, with the equipment order, deposit, host readiness, loan availability, hardware delivery, installation, customer acceptance, first cash receipt and repayment date on the same line. An executed customer contract helps a financier underwrite future receipts, while a signed financing commitment answers who pays the bills before those receipts exist. IREN disclosed a May 2026 GPU financing through a dedicated subsidiary, secured by equipment and customer-contract cash flows, with delayed draws aligned to Microsoft agreement delivery milestones and limited parent guarantees. (IREN FY2026 Form 10-K, as of October 19, 2026)

The detailed contract tests belong in compute offtake as credit; collateralizing compute covers the security and access rights. The sequence here asks a simpler question: at every date when cash must leave, which committed source supplies it?