From Curtailment To Cost: Four Capacity Questions For US Data Centers

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

Rymvard published four illustrative data center capacity scenarios on Oct. 3, 2026, describing constraints in Northern Virginia, Texas, Arizona and central Ohio. The examples show how grid connections, curtailment requirements, cooling limits and utility charges can affect capacity, but the company has not reported customer deployments or independently verified results.

Rymvard published four illustrative US data center capacity scenarios on Oct. 3, 2026, showing how grid-connection delays, curtailment rules, cooling limits and utility charges can make a facility’s headline power reservation differ from the capacity it can use, sell or afford, as explored in the original analysis. The examples cover Northern Virginia, Texas, Arizona and central Ohio; Rymvard says they are based on an illustrative estate, not a named customer or actual site outcome.

The company says its early-access product brings measured power, contracts, recovery reservations, cooling and demand together in a single ledger. The aim, as presented in the examples, is to make visible how a site’s commitments and operating limits relate to the power it actually draws. Rymvard has not supplied independent validation that the product improves capacity planning or changes operating results.

In Northern Virginia, Rymvard points to long waits for new utility connections and a possible gap between customer reservations and measured draw. It says some capacity available to sell in the near term may already be within a campus, rather than dependent on a new connection. The company does not identify a specific facility or quantify the gap.

The other examples concern different local constraints. Rymvard says Texas sites of 75 megawatts or more must accept curtailment under Senate Bill 6 when the grid operator sheds load, making it important to distinguish critical services from loads that could be reduced. In Arizona, the example focuses on cooling limits during the hottest afternoons. In central Ohio, it describes a tariff requiring certain new data centers above 25 MW to pay for at least 85% of subscribed power for up to 12 years.

Capacity Is More Than a Reservation

The scenarios address a practical gap between contracted or reserved power and capacity that a data center can reliably use, sell or afford. A delayed connection can hold back expansion; a curtailment obligation can affect operations during grid stress; hot weather can constrain cooling; and a tariff can leave a customer paying for subscribed power it does not draw.

Those distinctions can shape customer commitments, equipment deployment and cost forecasts. A consolidated record of demand and constraints could help operators understand the capacity they can offer, while clearer demand information may also help utilities and grid planners distinguish reservations from actual use. But a ledger cannot itself add grid supply, shorten connection queues or remove tariff obligations. Rymvard’s announcement describes a planning tool and a set of examples, not evidence that those wider outcomes have changed.

Four Markets, Four Constraints

Rymvard presents the scenarios as local examples, not a national capacity forecast. Northern Virginia’s example concerns connection timing and the difference between reserved and measured demand. Texas’s focuses on curtailment obligations; Arizona’s on cooling during extreme heat; and Ohio’s on the cost of subscribed power under a regulated utility tariff.

The Ohio reference is the AEP Ohio data center tariff in Public Utilities Commission of Ohio case 24-508-EL-ATA, with an order dated July 9, 2025, according to the supplied source material. Rymvard says its product is in early access and that the published screens and scenarios use an illustrative estate. The examples do not establish how often these constraints affect sites across each market or how large their financial effects are.

“Rymvard joins measured power, contracts, recovery reservations, cooling and demand into one ledger.”

— Rymvard

Customer Results Remain Unreported

Rymvard has not identified customers or specific sites using the product, disclosed measured results, or quantified any effect on costs, capacity planning or curtailment decisions. Its scenarios are illustrative and should not be treated as accounts of actual facilities or forecasts for the four markets.

The company has also not published pricing, detailed data inputs, integration information or verification methods. It says pricing is agreed with early-access partners. The available material does not show how the ledger handles site-specific contracts and measurements, or whether its information has been checked independently.

Evidence to Watch in Early Access

Rymvard says the product is available in early access and invites interested parties to contact contact@rymvard.com. It has not announced a broader release date, a pricing schedule or a named customer deployment.

The next useful evidence would be disclosed customer deployments and independently verifiable results, along with details on how site measurements, contracts and operating constraints are incorporated. Until the company provides those details, the four scenarios show the planning problems it aims to organize; they do not establish that the product has resolved them.

Key Questions

What did Rymvard announce?

Rymvard published four illustrative data center capacity scenarios covering Northern Virginia, Texas, Arizona and central Ohio, alongside a description of its early-access capacity ledger.

Do the scenarios describe actual data centers?

No specific customer or site is identified. Rymvard says the examples use an illustrative estate, not a customer site or reported operating outcome.

What constraints do the examples cover?

They cover utility connection delays in Northern Virginia, curtailment obligations in Texas, cooling limits in Arizona and a utility tariff affecting certain new data centers in central Ohio.

Has Rymvard shown that the product reduces costs or improves planning?

The announcement provides no quantified savings or independently verified results. It does not identify customer deployments or show that the product changed capacity-planning or curtailment decisions.

Primary source: Rymvard · via ThorstenMeyerAI.com