InfraComputeThe capital behind compute.
Recovery / InfraCompute research

What the risk controls actually cover

Insurance, cash reserves and replacement operators act on different failures. The value lies in the response path, including what happens before cash arrives.

Explore the analysis

Select the loss event

Physical damage

Property and interruption response

Review insured property, insured parties, deductibles and exclusions. Identify the cash provider before a claim is settled.

Conceptual framework. Select a stage to inspect it; actual rights and obligations depend on the transaction.

01

Write the failure before the solution

A risk register becomes useful when it explains how a loss reaches the borrower’s cash account. Begin with an event: delayed energisation, coolant damage, an unpaid customer invoice or an operator losing its technical team. Trace the operational interruption, the lost receipts, the cash needed to continue and the creditor’s resulting exposure. This gives each proposed control a defined job.

American Compute’s risk-management guide discusses appraisal, physical damage, operator continuity, customer payment and residual value. InfraCompute’s framework adds a response-time dimension. A protection that reimburses a loss months later may preserve ultimate recovery while doing little to meet next month’s power bill or debt payment.

02

Distinguish resilience, liquidity and loss transfer

Operational resilience seeks to prevent or shorten an interruption: tested maintenance, spare parts, suitable cooling and a replacement operator. Liquidity pays bills while the interruption is resolved. Insurance or contractual support may transfer a defined loss, subject to the relevant trigger, conditions, limit and exclusions. These functions can complement one another, but the existence of one does not establish the others.

For insurance, read the issued wording and schedule. Identify the insured equipment, insured parties, loss payee, deductibles, waiting periods and claims process. Check responsibility during transit, installation and normal operation. A general statement that the building is insured does not establish cover for a separately owned server fleet. Equally, a property policy should not be presumed to cover price declines or customer insolvency.

03

Test who can act on day one

A replacement operator needs more than a name in a presentation. Establish access to the facility, systems, licenses, support arrangements and customer permissions. Decide who can authorise the handover and how its costs are funded. Review whether the customer contract survives the change. A continuity plan can fail even when the replacement team is technically capable.

Residual-value protection needs its own test. Specify the assets, valuation date, disposal process, insured floor and counterparty. Distinguish a shortfall below a defined insured value from a promise to repay the entire loan. American Compute describes commercial products in its guide; those descriptions are not evidence that any particular InfraCompute-listed financing has that cover.

04

Stress combined failures

Run a combined scenario in which a rental-price decline reduces cash generation while several operators try to sell similar hardware. Add a service interruption and a delayed claim payment. Recalculate cash runway and net recovery after preservation, removal and disposal costs. A control deserves credit only for the loss it can address, at the time it can respond, for the creditor entitled to receive the benefit.

Apply the analysis

Questions for the credit paper

  1. What pays operating costs before a claim or guarantee payment is received?
  2. Can a replacement operator access the hardware, software and customer contract?
  3. Does the protection cover this exact loss, asset, time period and beneficiary?
Sources & scope

About this guide

Original InfraCompute analysis informed by the American Compute material below. The article structure, examples and interactive visuals are InfraCompute’s work. Source-specific findings remain attributed to American Compute; attribution does not imply affiliation or endorsement.

We reviewed the published edition and selected public references. We have not independently verified American Compute’s proprietary datasets, every market claim or confidential financing terms. Frameworks and hypothetical models describe questions to investigate; they do not establish protections in a particular financing. Legal and engineering conclusions depend on the relevant documents, system and jurisdiction.

Read our research methodology →
Next in the handbookWho benefits from a vendor backstop?
Randeep Bubbra

InfraCompute Weekly

The week in compute finance, read from the filings.

Deals, terms and the clauses behind them, for the people financing data centres, GPU clouds and the power behind them. By Randeep Bubbra.

Working on a GPU or data centre financing? Book 20 minutes with Randeep.

Fridays, one email. Work email only. Unsubscribe any time. Privacy.