Riot Platforms disclosed on August 10, 2026 that it had executed a Data Center Lease and Services Agreement with an unnamed leading frontier AI lab for 191 MW of critical IT capacity at its Rockdale, Texas campus. Riot expects approximately $9.1 billion of contract revenue over the initial term through June 2048. That figure is expected revenue over time, not an upfront payment, and the contracted capacity is not yet operational.
The delivery schedule calls for 96 MW in December 2027 and the remaining 95 MW by June 2028. For a finance technology or infrastructure finance lead, the question is what evidence should start acceptance and payment at each phase. The filing incorporates Riot’s transaction disclosure but does not attach the executed lease. Acceptance tests, cooling allocation, service measures, data handling, remedies and termination provisions are therefore not disclosed in the public materials.
What changed and what it means
Weak controls can start payment before capacity is usable, shift utility and outage costs, and make a 20-year commitment difficult or expensive to unwind.
- Decision affected
- Approve or defer a phased AI-capacity commitment only after acceptance evidence, power and cooling responsibilities, service levels, data boundaries and exit rights are tied to payment and renewal.
- Evidence in brief
- Riot’s 8-K, press release and presentation establish an executed 191 MW lease, phased delivery in December 2027 and June 2028, expected contract revenue and company-stated secured power.
- What remains unresolved
- The executed lease is not attached to the filing, so acceptance tests, cooling allocation, SLA metrics, data handling, remedies and termination rights are not disclosed.
- Next verification
- Tie each capacity phase to an objective test pack, payment commencement, dependency owners, service remedies and a funded transition plan.
Key takeaways
- Riot executed a 20-year agreement for 191 MW of phased critical IT capacity, with 96 MW expected in December 2027 and full deployment expected by June 2028.
- The $9.1 billion figure is expected contract revenue across the initial term, while the capacity still has to be built, commissioned and accepted.
- A Tier 3 description does not by itself prove that a completed phase meets the tenant’s workload, power, cooling or operating requirements.
- Finance technology leaders should tie payment and renewal to acceptance evidence, dependency ownership, service measures, data boundaries and executable exit rights.
What Riot signed, and what the public record does not show
Riot describes the project as a build-to-suit Tier 3 data center. The initial term runs through June 2048, with two five-year extension options. Its August presentation divides delivery into 96 MW and 95 MW phases. Riot also says the tenant’s basis of design has been incorporated, design and internal architecture are complete, delivery partners have been selected, required power has been secured, and a $573 million Morgan Stanley interim facility is funding early procurement while an investment-grade credit backstop is finalised. These are company-stated execution claims, not proof that either phase has passed acceptance.
The prior disclosed Rockdale state was 50 MW contracted to AMD. Riot reported in April 2026 that AMD had exercised an additional 25 MW option. Riot later said the first 25 MW had been commissioned and the second 25 MW was under construction. The new agreement raises disclosed contracted Rockdale capacity to 241 MW, but only the commissioned AMD capacity was operating when Riot made the August disclosure.
The public record establishes the commitment, capacity, timetable and company financing plan. It does not disclose who signs acceptance, which defects permit rejection, when rent or service charges begin, or which failures create termination rights. The framework below is Finance Circuit analysis for comparable agreements, not a claim that Riot’s lease lacks these provisions.
Tie phased capacity acceptance to test evidence and payment
Each phase needs an acceptance schedule that converts “megawatts delivered” into evidence a finance approver can inspect. It should identify the tested configuration, required load, measurement period, normal and backup modes, permitted variances, open defects and the person authorised to accept an exception. Substantial completion is not proof that the contracted IT load can run within the agreed power, cooling, network and security envelope.
Uptime Institute defines Tier III as concurrently maintainable, allowing planned maintenance without shutting down IT operations. Its separate constructed-facility certification verifies that a facility was built as designed and can meet defined performance requirements. Riot uses the term Tier 3, but the opened materials do not say Uptime awarded a design or constructed-facility certification. Finance should require the certification, independent test report or equivalent evidence made relevant by the contract.
Payment should follow the accepted unit, not a broad project date. The agreement should cover partial acceptance, withholding for failed capacity, retesting, defect retention and delay costs. Change control should prevent a late design change, denser rack profile or different cooling requirement from silently moving the acceptance baseline or reallocating cost.
Map power and cooling dependencies to named owners
Riot says required power has been secured and aligned with delivery milestones. A tenant approval pack still needs a dependency map from grid and interconnection through substations, switchgear, backup generation, UPS, distribution, cooling plant and the rack handoff. “Power available,” “facility capacity” and “usable critical IT capacity” are different states with different owners and acceptance dates.
The contract should record expected rack density, peak and sustained load, cooling technology, temperature and humidity envelope, water or fluid requirements, redundancy mode, curtailment treatment and maintenance windows. It should also allocate tenant fit-out, incremental infrastructure, efficiency shortfalls, utility changes and metered pass-through charges.
The data-center financing readiness gate separates sponsor commitment, financial close and construction draws. Tenant acceptance needs the same discipline after capital is committed: a financing milestone is not evidence that contracted capacity is ready for use or payment.
Define service levels at the workload boundary
A facility availability percentage is too remote from the finance workflow if the tenant cannot tell whether power, cooling or network service reached the agreed handoff. The service schedule should identify the measured point, source system, interval, exclusions and evidence retained. Measures may include delivered critical power, environmental compliance, network availability at the demarcation point, maintenance notice, incident response, restoration time and root-cause completion.
Remedies should match consequence. Credits may address isolated underperformance, but should not be the only remedy for repeated failure, a material security event, chronic capacity shortfall or a missed long-stop date. Finance should model substitute capacity, workload delay, duplicated migration cost and charges that continue during unavailability.
A 20-year term also makes technical change predictable. The agreement needs a governed route for new rack densities, liquid cooling, interconnects, security requirements and metering methods, including cost, downtime and any step-down or exit right if a change is rejected.
Set data boundaries before operations begin
Even when the tenant owns compute hardware and application data, the provider may handle access records, support tickets, incident evidence, capacity telemetry, network data and building-management information. The agreement should map ownership, permitted access, storage location, retention, sharing and deletion or return at exit.
NIST SP 800-144 concerns public-cloud outsourcing, not Riot’s lease, so it is not a contract standard for this transaction. Its guidance is useful by analogy: negotiated terms can address data ownership and exit rights, breach notification, tenant isolation, encryption and segregation, service reporting and responsibility boundaries.
The operating record should identify support roles, physical and logical access paths, incident-notification clocks, audit evidence, subcontractor changes and the line between facility telemetry and workload data. Broad confidentiality language without a system and log map can leave both teams unsure who may investigate an incident and what evidence must survive it.
Make exit rights executable and funded
A long-duration agreement should address persistent delivery delay, material capacity shortfall, repeated service failure, security breach, prolonged force majeure, insolvency, prohibited control changes and regulatory conditions that make continued use impracticable. The trigger and remedy are legal decisions, but finance should model their cash and operating effect before approval.
Transition assistance should cover service during migration, equipment removal or transfer, export of logs and configuration records, replacement-provider access, decommissioning, site restoration and extended-support pricing. Partial capacity reduction can matter as much as full termination when only one phase, hall or workload is affected.
The AI provider concentration and exit evidence framework adds a related test: a contractual option is not operational resilience unless dependencies are mapped, the move is budgeted and the handoff is rehearsed. For physical capacity, that rehearsal should include an alternative site, equipment and network sequence, minimum overlap, decision owner and tested elapsed time.
What finance technology leaders should verify now
| Control area | Evidence before approval | Finance decision |
|---|---|---|
| Phased acceptance | Test plan, measured results, defects, retest record and authorised certificate for the exact capacity unit | Start, defer or partially release payment |
| Power and cooling | Dependency map, workload profile, milestones, metering basis, redundancy tests and named owners | Accept cost allocation and delay exposure |
| Service levels | Handoff metrics, source telemetry, notice and restoration clocks, exclusions, escalation and remedies | Approve the service-risk limit and remedy |
| Data boundaries | Data and log map, access roles, location, retention, audit rights and deletion or return process | Approve the security and evidence boundary |
| Exit rights | Triggers, step-down rights, transition duties, cost model, alternative capacity and funded rehearsal | Approve the initial term, renewal or expansion |
Riot’s disclosure separates an executed commercial commitment from future phased deployment. Finance technology leaders should preserve that distinction. Contract value, a delivery date and a Tier description are starting facts. Payment and renewal should follow inspectable evidence that capacity works, dependencies are owned, service and data boundaries are measurable, and the exit path can be executed.
