The disclosure and our analysis
What Lambda announced
Lambda announced September 27 that it plans a data center at MidAmerica Industrial Park in Mayes County, Oklahoma. Its release identifies Grand River Dam Authority and MidAmerica as having selected Cloverleaf Infrastructure to prepare the site. This establishes a development announcement, not completed construction or customer availability. [1]
The company forecasts $500 million in taxes over ten years at current rates. That is a tax estimate, not the project's construction budget, contracted revenue or lease price. It describes planned closed-loop cooling and a commitment to pay its energy costs. Those are company statements, not independently verified operating results. [1]
Capacity and transaction limits
The announcement does not disclose MW, customer pricing, a signed tenant lease, or a delivery date. It therefore establishes neither critical IT load nor utility service capacity. Searches for related GRDA, MidAmerica and Cloverleaf disclosures did not produce a project-specific contract for review. The commercial arrangement among the participants remains unverified beyond the roles Lambda describes. [1]
Colocation Scout buyer analysis
For infrastructure buyers, the announcement adds a location to monitor. It does not yet supply enough information to compare a delivered service with another provider's offer.
Start by determining what would actually be sold. A cloud service, a dedicated compute deployment and a colocation lease can involve different counterparties, operating responsibilities and acceptance criteria. A developer's participation does not establish that it will be the customer's service provider or landlord.
The next useful document is a project-specific delivery plan. Ask for phase boundaries, utility milestones, commissioning requirements and the remedies attached to a missed date. Separately request the usable IT power basis, cooling envelope and network options for the proposed service. Do not infer these from an economic-impact forecast or the industrial park's broader infrastructure.
Resource commitments also need to be translated into procurement terms. A statement about who pays energy costs is not a customer tariff. Buyers should establish how energy and demand charges flow through their contract, which upgrade costs are included, and whether any charges can change after signature.
Likewise, evaluate cooling through design evidence and operating commitments rather than a single label. Request the boundaries of the proposed system, expected consumption under specified conditions, maintenance requirements and the responsibility for meeting customer thermal requirements. The analysis should match the planned workload rather than assume every liquid-cooled deployment has the same needs.
What would make this actionable
A named phase with a verified delivery window, documented power arrangements and a written customer offering would support a more concrete comparison. Until those are available, buyers with near-term requirements should keep this project on a development watchlist and evaluate alternatives with confirmed service commitments.
Evidence date: September 27, 2026; reviewed September 28. The distinction between announced development and available capacity should remain in any later update.