What is project finance?

Project finance is the practice of financing a single asset or project on its own merits. Capital is advanced to an entity created to hold that project and nothing else, it is repaid out of the cash flow the project generates, and it is secured on the project's assets, contracts and accounts. Recourse to the sponsor that developed the project is limited, and after construction is complete it is often eliminated altogether.

"Non-recourse" is a term of art rather than a literal description. Almost every structure retains recourse for a defined set of things — completion of the build, cost overruns, fraud, environmental liabilities, breach of specific undertakings. What is genuinely non-recourse is the operating risk: once the asset is built and performing, if the cash flow disappoints, the loss sits with the project's own capital rather than travelling back to the sponsor's balance sheet.

The trade being made is visible in that sentence. The sponsor gives up ordinary corporate flexibility — the project entity is tightly covenanted, its cash is controlled, its distributions are conditional — and receives in exchange the ability to finance a project larger than its own balance sheet would support, without putting the rest of its business behind it.

The two are often compared on price, which is the least informative axis. They differ in what is being examined.

A corporate lender examines a company: its history, its diversification, its ability to generate cash from many sources, and its capacity to absorb one thing going wrong. A project lender examines a structure: a defined set of contracts, with no history, no diversification, and one source of cash. It has no operating record to lean on, so it substitutes contractual certainty for track record — which is why project financings are documented so much more heavily than corporate ones for the same amount of money.

Project finance is not available on request. It becomes available when four things are true, and it is unavailable — at any price — when they are not.

A ring-fenced entity. The project has to sit in a vehicle that holds it and nothing else, so the cash flow being financed cannot be diverted to other obligations and other businesses' problems cannot reach it. What makes that separation real rather than nominal is the subject of [special-purpose vehicle](special-purpose-vehicle).

Contracted revenue. Something has to fix what the project will be paid and by whom. That is [offtake](offtake), and where the obligation is firm rather than consumption-linked — see [take-or-pay](take-or-pay) — it does far more work.

Every material risk allocated by contract. This is the discipline that distinguishes project finance from ordinary secured lending. Construction risk goes to a contractor under a fixed-price agreement. Operating risk goes to an operator. Supply risk goes to a fuel or equipment supplier. Volume risk goes to the offtaker. Whatever is left unallocated is held by the project's equity, and a project with too much left over does not get financed on this basis.

Cash flow that covers the obligation with headroom in every period. Sizing runs backwards from the cash flow rather than forwards from the cost, using the coverage test set out at [debt service coverage ratio](debt-service-coverage-ratio).

The build itself is normally funded separately and refinanced on completion — the sequence is described at [construction loan](construction-loan).

Project finance suits assets that are long-lived, predictable to operate, and contracted to creditworthy buyers for a long time. Measured against [the four layers of a data center](the-data-center-capital-stack), it fits some of them well and one of them badly.

Generation and power equipment is the natural fit and the oldest application of the technique. A turbine with a capacity payment behind it is close to the textbook case: long asset life, mature operating history, an obligation that pays for availability.

Shell and fit-out fits well once complete and contracted. A facility with a long lease to a strong tenant produces exactly the kind of durable, documented cash flow the structure was built for — which is why data-center capital is frequently described as closer to corporate credit than to real estate.

Land and interconnection rarely supports it on its own, because a site produces no cash flow until something is built on it. It is typically financed by equity until it has been developed into something that does.

Compute is the misfit, and the mismatch is structural rather than a matter of degree. A financing technique built around a twenty-year asset with a fifteen-year contract does not transfer to a three-year asset whose value is set by another company's product roadmap. Forcing all four layers into one project financing prices every layer off the least comfortable one — the argument set out at [tenor mismatch](/compute/tenor-mismatch-compute-and-infrastructure), and the reason the layers are separated in the first place.

Continuum structures deals along those lines: establishing which layers can carry a project-financed shape, which need equipment or lease treatment, and coordinating the contracts that let each layer stand on its own.