What Is a DSCR Covenant? a Guide for GPU Cloud Operators
Summary
- A DSCR covenant is a loan-document promise to keep cash flow at or above a set multiple of debt service on each test date.
- Filed GPU facilities at IREN, Nscale and CoreWeave set levels between 1.05x and 1.40x, some layered into sizing, cash-trap, prepayment and default levels.
- In those facilities, a miss can trap cash or force prepayment. Equity or a new or renewed offtake contract can cure it before default.
Introduction
A GPU term loan with a DSCR covenant comes with a coverage test that runs every month or quarter for the life of the debt. The definition in the credit agreement decides whether a slow collection month becomes a cash trap.
GPU debt puts more pressure on that test than a building loan does. Revenue comes from offtake contracts that can end before the loan matures. Principal amortizes from the first month, so debt service is heaviest while the deployment is newest.
This guide sets out the debt service coverage ratio formula on a GPU deployment and how the test runs. It covers the three coverage levels in filed GPU facilities, what a breach triggers, how cures work and how to keep headroom through year one.
What a DSCR Covenant Measures on a GPU Deployment
A DSCR covenant is a promise in the loan documents to keep debt service coverage at or above a stated minimum on each test date. The ratio divides cash flow available for debt service by scheduled principal plus interest for the same period. At 1.0x, cash exactly covers the payments, and anything above that is cushion.
The formula comes from real estate lending. The Comptroller of the Currency's Comptroller's Handbook (March 2022) defines DSCR as cash flow or net operating income (NOI) divided by the debt service. On a GPU deployment, the numerator becomes collections under the offtake contract less colocation, power and other operating costs.
Nscale's February 2026 loan agreement defines the numerator as offtake cash flows less data center costs and senior expenses. Take an illustrative deployment collecting $1.5 million a month after those costs, against $1.2 million of scheduled principal and interest. Its DSCR is 1.25x, so collections would have to fall 20% before the payments went uncovered.
The covenant is an ongoing test, and the same ratio does a second job at closing. Lenders use projected DSCR to size the loan, a step our guide to how GPU loans are underwritten covers. Nscale's terms show both uses: new advances are sized to at least 1.20:1.00, and a cash trap starts below 1.15:1.00.
How the Test Runs: Frequency, Window and Cash Basis
The test definition matters as much as the level, and filed GPU facilities measure coverage in different ways. CoreWeave's DDTL 5.5 credit agreement (August 2026) sets a 1.35x minimum, tested monthly on the trailing three months. A DDTL is a delayed draw term loan, drawn in stages. IREN's filing (May 2026) sets 1.05:1.00 for IE US Hardware 3, tested as of each quarterly determination date.
| Facility (filing date) | Level tested (that facility's term) | Test frequency | Measurement window |
|---|---|---|---|
| CoreWeave DDTL 5.5 (Aug 2026) | 1.35x minimum | Monthly | Trailing three months |
| IREN IE US Hardware 3 (May 2026) | 1.05:1.00 minimum | Each quarterly determination date | Not covered |
| Nscale (Feb 2026) | 1.15:1.00 cash-trap level | Each quarterly payment date | Trailing three months of offtake cash flows |
The date of the first test matters too, because a new deployment needs time to reach full collections. CoreWeave's DDTL 4.0 (March 2026) tests 1.15x from the first full month after commitments fall to zero or June 30, 2027, whichever is earlier. The DDTL 3.0 amendment (December 2025) sets that facility's 1.40x test to begin after October 1, 2027.
Lambda's facility ties the start of repayment to stabilization. Morningstar DBRS rated the $1.008 billion Lambda Compute I DDTL A (low) in October 2026. Each GPU tranche amortizes after stabilization at a minimum DSCR of 1.20x. The agency describes the offtake as take-or-pay with no re-leasing exposure (see take-or-pay contracts explained).
A trailing three-month window averages one slow month against two normal ones, while a single-period test counts that period alone. On a cash-collected basis, a March invoice paid in April moves into the next test period. A billed basis counts it when issued. DDTL 5.5 counts cash deposited into a designated account, so a late payment under the offtake contract can land in the wrong test window.
The Three Coverage Levels in a GPU Facility
Nscale's and IREN's facilities each carry more than one coverage number, and each number does a different job. Nscale pairs a sizing level at funding with a cash-trap level, and IREN pairs two prepayment triggers with a lower maintenance level.
The sizing level decides how much each draw can borrow. Nscale's credit agreement (February 2026) sizes new advances to a DSCR of at least 1.20:1.00. Among the terms cited here, that is the only sizing level.
The cash-trap or prepayment level sits above the floor and pulls cash toward the loan before a breach. Nscale's agreement defines a Cash Trap Event as historical DSCR below 1.15:1.00, and four consecutive trapped determination dates become a mandatory prepayment event. IREN requires mandatory prepayment if DSCR falls below 1.10:1.00 for six consecutive months. It also requires one if projected DSCR for the third and fourth tranches would be below 1.20:1.00.
The maintenance level is the floor, and missing it is a covenant breach. IREN's minimum is 1.05:1.00, subject to equity cure rights. CoreWeave discloses one level per facility: 1.15x for DDTL 4.0, 1.35x for DDTL 5.0 (May 2026) and DDTL 5.5, and 1.40x for DDTL 3.0.
Every figure in the table is that facility's term, taken from its filing. Cells marked "Not covered" are levels this article doesn't address.
| Facility (filing date) | Sizing level | Cash-trap or prepayment trigger | Maintenance minimum |
|---|---|---|---|
| Nscale (Feb 2026) | At least 1.20:1.00 on new advances | Below 1.15:1.00; four consecutive dates trigger mandatory prepayment | Not covered |
| IREN IE US Hardware 3 (May 2026) | Not covered | Mandatory prepayment if below 1.10:1.00 for six consecutive months, or if projected DSCR for third and fourth tranches is below 1.20:1.00 | 1.05:1.00 |
| CoreWeave DDTL 3.0 (Dec 2025 amendment) | Not covered | Not covered | 1.40x |
| CoreWeave DDTL 4.0 (Mar 2026) | Not covered | Not covered | 1.15x |
| CoreWeave DDTL 5.0 (May 2026) | Not covered | Not covered | 1.35x |
| CoreWeave DDTL 5.5 (Aug 2026) | Not covered | Keyed to contract events | 1.35x |
The distance between these levels is your headroom. An Nscale advance sized at exactly 1.20:1.00 has 0.05x before cash is trapped. IREN's terms leave 0.05x between the 1.10:1.00 prepayment trigger and the 1.05:1.00 floor. Each number is one borrower's agreement with its lenders, so read them as evidence of what has been signed.
What a Breach Triggers and How Cures Work
In the Nscale, IREN and CoreWeave DDTL 5.5 terms cited here, a miss can trap cash or force prepayment. An uncured breach becomes an event of default. Each step below comes from one of those facilities, and each gives the lenders more control over the deployment's cash.
- Cash trap. Nscale's trap starts below 1.15:1.00, and DDTL 5.5's starts on contract events.
- Mandatory prepayment. Nscale's trap becomes a prepayment event after four consecutive dates, and IREN's applies after six months below 1.10:1.00.
- Cure. IREN's covenant carries equity cure rights, and DDTL 5.5 sets a cure period, the window to fix a breach.
- Event of default. In DDTL 5.5, a DSCR breach left uncured past the cure period is an event of default.
- Acceleration. DDTL 5.5's lenders can then accelerate, meaning they demand the full balance at once.
- Enforcement. DDTL 5.5's lenders can also enforce against the collateral under the security documents.
CoreWeave's DDTL 5.5 offers two cure routes: new equity, which counts toward the ratio, or a qualifying new or renewed offtake contract. The second route ties the cure to the revenue the test measures. In that facility, the cash trap keys off contract events, such as an offtake contract breach, and a DSCR breach goes through the cure process.
Equity cures can come with limits on how often you can use them. DLA Piper (May 2026) reports that restrictions on cures in consecutive quarters are common in UK and European mid-market and private-credit deals. Aggressive deals in that segment allow back-to-back cures, with no more than two in any 12-month period. The firm calls four cure rights over a facility's life the market norm.
Those figures describe UK and European mid-market and private credit, and no GPU-specific dataset sits behind them. Count the cure rights in your own agreement before you need one.
How to Stay Above the Line
Under straight-line amortization, coverage is tightest in year one, so the first year sets your headroom. Equal principal payments mean interest, charged on the outstanding balance, is highest while the loan is new.
Illustrative: a typical market loan with assumed terms, not USD.AI's terms.
The example assumes a $40 million, four-year loan at 12% annual interest (1% a month on the balance). Principal is paid in equal monthly amounts of $833,333.
| Year | Annual debt service | DSCR at flat $18.0M cash | Cash falling 10% a year | DSCR with falling cash |
|---|---|---|---|---|
| 1 | $14.25M | 1.26x | $18.0M | 1.26x |
| 2 | $13.05M | 1.38x | $16.2M | 1.24x |
| 3 | $11.85M | 1.52x | $14.6M | 1.23x |
| 4 | $10.65M | 1.69x | $13.1M | 1.23x |
With flat cash of $18 million a year, coverage climbs each year as debt service falls, reaching 1.69x in year four. If cash falls 10% a year, coverage stays between 1.23x and 1.26x. Falling debt service absorbs falling revenue only while revenue declines no faster than debt service, which drops about 8% to 10% a year here.
Renewal risk is the second pressure point. CoreWeave's DDTL 5.5 announcement (August 2026) describes about five years of debt against offtake contracts averaging about three years. In our view, keeping that covenant in the later years depends on re-contracting at similar economics, which our guide to how offtake agreements work explains.
Rental prices move in both directions, so model a downside case alongside the base case. SemiAnalysis's H100 one-year contract index rose from $1.70 to $2.35 per GPU-hour, October 2025 to March 2026, per our post on rising GPU rental prices. A fall of similar size at renewal would cut straight into the numerator.
Most of your headroom is set before you sign. Five steps keep the most room between your deployment's cash and the covenant line:
- Negotiate the definition. Agree the cash basis, the test window and which costs count as operating costs.
- Match the first test to stabilization. Set the first test date after the deployment reaches full collections.
- Keep a debt-service reserve. A funded reserve covers payments if an offtake customer pays late.
- Renew contracts ahead of test dates. Sequence renewals so no contract expiry lands inside a test window.
- Model base and downside cases. Run the covenant through year one under lower rental rates and slower collections.
Conclusion
The level, test window, cash basis and cure path together decide how much room you have under a DSCR covenant. Under USD.AI's underwriting standards, each loan is tested every quarter against a minimum DSCR of 1.15x, measured on the cash collected in the quarter. That compares with a monthly trailing three-month test in CoreWeave's DDTL 5.5 and quarterly determination dates at IREN.
From the first quarter below 1.15x, a cash trap and sweep applies, and cash beyond scheduled debt service goes toward the loan. Two consecutive breaches open a cure period, in which the operator makes a mandatory partial prepayment that brings the loan back into compliance. If the breach isn't cured, the loan is in default. The lenders can, at their option, accelerate and enforce against the servers, the offtake contract and the revenue accounts.
A three-month debt-service reserve, funded by the operator at closing, covers payments if collections are delayed. GPU financing through USD.AI applies this same structure to every deployment.
FAQ
How much DSCR is good for a GPU loan?
Any DSCR above 1.0x covers scheduled payments, and filed GPU facilities set minimums between 1.05x (IREN, May 2026) and 1.40x (CoreWeave DDTL 3.0, December 2025). A good DSCR keeps clear headroom above your own covenant through year one, when debt service is highest under straight-line amortization.
What does a DSCR below 1.0 mean?
A DSCR below 1.0 means cash available for debt service doesn't cover the scheduled payments for that period. A reserve or new equity has to cover the gap, and the shortfall triggers the cash trap, cure or default steps in the credit agreement.
Is a DSCR covenant the same as a DSCR loan?
No. A residential DSCR loan is a rental-property mortgage qualified on the property's income. A DSCR covenant is an ongoing coverage test in a commercial credit agreement, such as a GPU term loan.
Editor Notes
- Cluster posts to link once live: gpu private credit (CoreWeave spreads), gpu loan rates, gpu depreciation, spv financing.
- Open items held back pending confirmation: Nscale's reported 1.05:1.00 maintenance minimum and its equity-cure caps; S&P figures for IS AN03 LLC (1.20x distribution test, 1.075x sweep).
- Facts held back by brand rules: The Loan terms rule bars stating a minimum DSCR. USD.AI's 1.15x quarterly test appears only because the reviewer approved it in the Nov 11, 2026 review, with the usd.ai underwriting page as source.
- Dropped per review: Lighthouse portfolio figures, the >$25B data points figure, SemiAnalysis and Ornn index figures (other than the one-year contract move linked through the Rent Is Due post) and the EthiFinance figure.
- Loan terms withheld: No cure length, fees, payment waterfall or sweep percentage is stated, per the Loan terms rule.
- Reviewer-added internal links: usd.ai/blog/gpu-loan-underwriting, /take-or-pay-contract and /offtake-agreement were added by the reviewer in the outline. Each returned a live page with a matching title on Nov 11, 2026; confirm again before publishing, and replace any that isn't live with an editor note, per the writing rule.
