QumulusAI's $71.9 million compute deal reaches billing, while expansion awaits delivery

QumulusAI's $71.9 million compute agreement has crossed an important boundary: the supplier says the contracted hardware is serving its customer and generating bills. That is company-reported delivery evidence, not independent verification of operational performance. It is also an October development, not a newly signed November transaction.

The company announced the three-year agreement on July 28 with an unnamed AI inference platform. It covered NVIDIA Blackwell B200 and B300 capacity for production workloads, with renewal options. At announcement, customer availability was expected during the third quarter of 2026. S1

Deployment came in stages. A September 15 update said the B200 portion had been handed over on September 8, while B300 deployment remained unfinished. The distinction matters: completion of one hardware tranche did not establish delivery of the entire agreement. S2

On October 15, QumulusAI reported that the final B300 handoff occurred at its Kansas City site on October 1. It said every GPU under the agreement was then in production and billing. The release did not disclose the contract's GPU count or the customer's power allocation. S3

The same customer separately signed a $211.9 million, three-year take-or-pay expansion announced September 29. That capacity was targeted for early 2027. Two optional one-year extensions, each valued at $70.6 million, sit outside the initial commitment. The original contract and expansion total $283.8 million, but that sum does not describe compute already delivered. S4, S3

For buyers and lenders, the distinction is practical. Delivery can reduce construction and commissioning uncertainty; it does not establish utilization, payment collection or customer credit quality. Those judgments require information these announcements do not provide.

A further qualification concerns timing. The final October handoff followed the original third-quarter availability target. That comparison does not prove a contractual breach: the public releases do not establish contractual deadlines, remedies or whether customer-approved changes altered the delivery timetable.