🔍 Read the full analysis: Grid Queues, Curtailment And Tariffs: Four Hard Capacity Questions For US Data Centers on Rymvard
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR

Rymvard published four illustrative US data center capacity scenarios on Oct. 3, 2026, covering Northern Virginia, Texas, Arizona and central Ohio. The examples show how grid connection delays, curtailment rules, cooling limits and a utility tariff can make usable or sellable capacity differ from a site’s headline power reservation.
Rymvard published four illustrative data center capacity scenarios on Oct. 3, 2026, showing how grid connection delays, emergency curtailment, cooling constraints and utility tariff obligations can limit capacity operators can sell or use. The early-access product combines power measurements, contracts, recovery reservations, cooling and demand in a single ledger; the company says the examples use an illustrative estate, not a customer site or outcome.
The scenarios focus on Northern Virginia, Texas, Arizona and central Ohio, where different constraints can complicate the meaning of a facility’s stated capacity. Rymvard says that in Northern Virginia, new utility connections can take years. It also describes existing reservations whose measured draw remains below the amount customers reserved, meaning capacity available to sell this year may already be within the campus rather than dependent on new connections.
In Texas, the company points to Senate Bill 6, signed in June 2025. Under the law as described by Rymvard, sites of 75 megawatts or more must accept curtailment when the grid operator sheds load. Operators therefore need to distinguish equipment supporting critical services from loads that could be reduced. The example describes an operational planning issue; it does not report a particular curtailment event or facility response.
Rymvard says that cooling can set the limit in Arizona on the hottest afternoons, while in central Ohio a tariff approved by the Public Utilities Commission of Ohio requires certain new data centers above 25 MW to pay for at least 85% of their subscribed power for up to 12 years. The company says its ledger brings these types of constraints and commitments together. Its pricing is not published and is agreed with early-access partners.
Power planning / US data centers / Oct. 3, 2026
Grid Queues, Curtailment and Tariffs: Four Hard Capacity Questions for US Data Centers
A site’s headline power reservation can differ from the capacity it can reliably use, sell, or afford. Rymvard’s four illustrative scenarios show how connection delays, grid rules, cooling limits, and tariffs complicate the number.
One capacity question, four different answers
These are illustrative examples, not a national forecast. Each market highlights a constraint that can separate reserved power from usable or sellable capacity.
Northern Virginia
New utility connections can take years. For existing reservations, measured draw may sit below what customers reserved, so near-term saleable capacity could already be on campus.
Question: What is reserved versus drawn?Texas
Rymvard describes Senate Bill 6, signed in June 2025: sites at or above 75 MW must accept curtailment when the grid operator sheds load.
Question: Which loads can be reduced?Arizona
On the hottest afternoons, cooling performance can set the practical operating limit, even where a site’s power reservation appears sufficient.
Question: How does heat bound capacity?Central Ohio
A tariff approved by the Public Utilities Commission of Ohio requires certain new data centers above 25 MW to pay for at least 85% of subscribed power.
Question: What does unused power cost?Rymvard says the Ohio commitment can apply for up to 12 years under the AEP Ohio data center tariff in PUCO case 24-508-EL-ATA; the order is dated July 9, 2025. Texas is described here as an operational planning issue, not a report of a specific curtailment event.
Capacity beyond the grid connection
Rymvard says its early-access product brings measured power, contracts, recovery reservations, cooling, and demand into a single ledger. The goal is to make the commitments and physical limits behind capacity visible together.
A ledger can clarify where a gap comes from. It does not itself add grid capacity, shorten utility queues, reduce heat, or remove tariff obligations.
“Rymvard joins measured power, contracts, recovery reservations, cooling and demand into one ledger.”— Rymvard
Inputs brought into one view
What the announcement establishes
The examples explain the planning problem Rymvard wants to organize. They do not yet establish customer results or product impact.
Stated by Rymvard
- Four illustrative scenarios cover Northern Virginia, Texas, Arizona, and central Ohio.
- The product is running in early access and combines operational and contractual information.
- The screens use an illustrative example estate; no customer, site, or outcome is identified or implied.
Not yet reported
- Named customer deployments, measured savings, or independently verified outcomes.
- Whether the ledger has changed forecasts, costs, or curtailment decisions.
- Detailed data inputs, integrations, verification methods, or site-level financial effects.
What would strengthen the case
Customer evidence showing how the product changed capacity forecasts or operating choices, with enough detail to assess the methods and results.
Commercial status
Rymvard says access is available to early partners. Pricing is not published and is agreed with those partners. No broader release date or pricing schedule has been announced.
From reservation to operational decision
A useful capacity view has to connect a paper commitment to physical conditions and the choices operators can make.
What power is reserved, subscribed, or contractually promised?
What is the site drawing, and what can cooling sustain?
What do queue timing, curtailment, and tariffs require?
What capacity can be used or sold with confidence?
A useful frame; results remain unproven
Where the case is strongest
A shared record of demand, contracts, cooling limits, and recovery reservations could help explain why nominal capacity differs from capacity available to customers. The four examples make that distinction legible without claiming every market faces the same constraint.
What remains uncertain
Combining information does not create power or remove local constraints. Without named deployments or checkable outcomes, it is difficult to judge whether the ledger materially improves decisions over existing tools and processes.
What to know at a glance
What did Rymvard announce?
Four illustrative US data center scenarios published Oct. 3, 2026, alongside its early-access capacity ledger.
Which markets are covered?
Northern Virginia, Texas, Arizona, and central Ohio, each illustrating a different capacity constraint.
Are these customer sites?
No. Rymvard says the examples use an illustrative estate and imply no customer, site, or outcome.
What does the Ohio tariff require?
For certain new data centers above 25 MW, at least 85% of subscribed power is payable for up to 12 years, as described by Rymvard.
Is the product generally available?
Rymvard says it is in early access; a broader release date has not been announced.
What does it cost?
Prices are not published; terms are agreed with early-access partners. Contact contact@rymvard.com.
Capacity Beyond the Grid Connection
The examples matter because a data center’s contracted or reserved power may not equal the amount of capacity it can reliably use, sell, or afford. A long wait for a new connection can constrain expansion; curtailment requirements can affect which services continue during grid stress; heat can limit cooling performance; and a tariff can require payment for subscribed power even when a site draws less.
For operators, those differences can shape customer commitments, equipment deployment and cost forecasts. For utilities and grid planners, clearer information about actual demand and flexible loads could help distinguish reserved capacity from the power a facility draws. Rymvard presents its ledger as a way to assemble that information, but the announcement does not provide independent validation, quantified savings or evidence that the product changes grid outcomes.
Products Worth Considering

Apple MacBook Air 13-inch with M5 Chip, 16GB Memory, 512GB SSD, Liquid Retina Display, and 12MP Center Stage Camera – Midnight

Samsung 32 Odyssey G5 QHD Gaming Monitor

LG 27GR83Q-B 27-inch Ultragear QHD IPS Gaming Monitor
As an affiliate, we earn on qualifying purchases.
Four Markets, Different Constraints
The scenarios are not a single national capacity forecast. They describe four local conditions that Rymvard says should be considered together with measured power and contractual commitments. Northern Virginia’s example concerns the timing of utility service and the gap between reserved and measured demand. Texas’s centers on a state law and curtailment obligations for larger sites. Arizona’s focuses on cooling during extreme heat, while Ohio’s concerns the cost of subscribed power under a regulated 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. Rymvard says its product is running in early access, but the screens and scenarios it published are based on an illustrative example estate. No customer, site or result is identified or implied.
“Rymvard joins measured power, contracts, recovery reservations, cooling and demand into one ledger.”
— Rymvard
Product Evidence and Site Results
The announcement does not identify customers using the product, disclose measured results, or quantify whether the ledger has improved capacity planning, lowered costs or changed curtailment decisions. The scenarios are illustrative, so they should not be read as accounts of a specific campus or as forecasts for each market. Rymvard also does not publish prices, saying terms are agreed with early-access partners.
Further details about the product’s data inputs, integrations, verification methods and use in operational decisions are not provided. The examples also do not establish how often the described constraints occur across each market or how large their financial effects may be at individual sites.
Early Access and Further Validation
Rymvard says the product is available in early access and invites interested parties to contact contact@rymvard.com. The company has not announced a broader release date, pricing schedule or named customer deployment. Its website is listed at https://rymvard.com/.
The next evidence to watch for is whether Rymvard reports customer deployments or independently verifiable outcomes, and whether it explains how its ledger handles site-specific measurements and contracts. Until then, the four examples are best understood as demonstrations of the problems the product aims to organize, not proof of results.
Where I land
I read this as a useful framing of a real planning problem, not yet evidence that Rymvard solves it. A single record of measured demand, contracts, cooling limits and recovery reservations could help operators see why nominal capacity differs from capacity available for customers. The four examples make that gap legible without claiming the same constraint applies everywhere.
The strongest counterargument is that a ledger does not itself create grid capacity, shorten utility queues, reduce heat or remove tariff obligations. Without named deployments or independently checkable results, it is hard to judge whether combining the information materially improves decisions over existing tools and processes. I would revise my assessment if the company published customer evidence showing how the product changed capacity forecasts or operational choices, with enough detail to assess the method and results.
Source: Rymvard
Key Questions
What did Rymvard announce?
Rymvard published four illustrative US data center scenarios on Oct. 3, 2026, and described its early-access capacity ledger, which combines measurements and operational and contractual information.
Which markets do the scenarios cover?
The examples cover Northern Virginia, Texas, Arizona and central Ohio, with a different capacity constraint highlighted for each.
Are the scenarios based on customer sites?
No. Rymvard says the screens come from its running product using an illustrative example estate. The company says no customer, site or outcome is implied.
What does the Ohio tariff require?
As described by Rymvard, new data centers above 25 MW must pay for at least 85% of subscribed power for up to 12 years under the AEP Ohio tariff approved in PUCO case 24-508-EL-ATA.
Is Rymvard’s product generally available, and what does it cost?
Rymvard says the product is in early access. It publishes no prices; pricing is agreed with early-access partners.
Source: Rymvard
