Ohio Lawmakers Set to Vote on State’s First Data Center Rules
Ohio lawmakers will vote Wednesday on House Bill 646, the state’s first data center rules. The bill would cut the sales tax exemption for new projects to 50%, limit local abatements to 50%, require data centers over 250 MW to bring their own power, and set statewide water-use standards with annual reporting. Supporters cite reform; the Ohio Chamber of Commerce warns it could hurt competitiveness, while environmental groups say it lacks enforcement details.
How this was made

The 30-second read
Why it matters
The bill’s core changes—halving sales-tax/local abatements for new projects, requiring data centers to shoulder connection costs via data-center-specific rates, and mandating water-use reporting and conservation measures—could materially affect economics for future Ohio builds. However, the largest hyperscalers’ long-dated sweetheart agreements are explicitly excluded, reducing immediate impact on their existing commitments.
Market read
Traders should focus on whether the Wednesday vote meaningfully changes expected costs for future Ohio data-center expansion, and whether utilities’ rate frameworks could shift earnings sensitivity for Ohio-regulated utilities.
What to watch
The article flags enforcement gaps (no clear penalty authority, unclear water-rate and wastewater-rate impacts). If enforcement is weak or delayed, the practical cost impact could be smaller than investors fear; conversely, utilities’ rate-design details could swing outcomes more than the headline tax cut.
Background
HB 646 is Ohio’s first attempt to regulate data centers, addressing sales-tax exemptions, utility cost allocation, and statewide water-use standards.
Ticker impact
HB 646 would cut Ohio’s sales-tax break for future data centers, but Amazon’s sweetheart agreements into the 2050s are explicitly not impacted.
Limited direct read-through; any market reaction would likely be second-order via sector sentiment on data-center regulation.
The article states Amazon’s agreements extending into the 2050s are not affected, reducing immediate earnings sensitivity; however, the policy could still affect expectations for future Ohio buildouts and peers’ expansion plans.
The bill would halve the sales-tax break for future data centers, but the article notes Meta’s sweetheart agreements into the 2050s are not impacted.
Low probability of a direct price move from this article alone; any effect would be through broader regulatory/cost expectations for data-center expansion.
The article explicitly exempts Meta’s long-dated agreements, limiting direct earnings/cash-flow sensitivity; the main uncertainty is how much future Ohio growth depends on new, non-grandfathered projects.
Ohio regulators required new data centers in AEP Ohio’s territory to shoulder more of the costs they create, and HB 646 would take that approach statewide.
Directionally mixed: could improve cost assignment to data centers, but may also pressure rate design and demand assumptions; net effect uncertain without tariff details.
The article describes prior PUC actions in AEP territory and proposes statewide ratemaking, but does not specify AEP’s financial exposure or the final rate mechanics.
Regulators ordered FirstEnergy’s Ohio utilities to develop similar rules on assigning future grid costs to data centers, and HB 646 would codify a statewide framework.
Unclear; could be modestly positive for cost recovery if data centers pay more, but could also reduce demand growth or increase compliance costs.
The article provides policy direction and references regulator orders, but no quantitative impact on FE’s earnings, capex, or tariff outcomes.
Market effects
Potentially raises the cost and compliance burden for new Ohio data-center projects (tax exemption cut, water standards, and data-center-specific utility rates), which can shift capex siting and power procurement strategies across the sector.
Could alter Ohio’s attractiveness for future data-center expansions and influence how quickly utilities build grid infrastructure for large loads.
Moderate: while Ohio is one state, the policy template (tax, ratemaking, water standards) can be read across to other US jurisdictions considering similar data-center regulation.
Counterpoint
Because the sweetheart agreements for Amazon/Google/Meta into the 2050s are not impacted, the bill may have limited immediate financial effect on the largest hyperscalers, making the market reaction more about future incremental projects than current cash flows.
Key entities
- legislationHouse Bill 646
Ohio’s proposed first data-center rules: cuts sales-tax exemption to 50% for future projects, sets water-use standards, and creates data-center-specific utility rates.
- regulatorPublic Utilities Commission of Ohio
Previously required new data centers in AEP Ohio territory to shoulder more costs and ordered FirstEnergy’s Ohio utilities to develop similar rules.
- companyVistra
Mentioned via Meta’s announced arrangement to upgrade the Perry Nuclear Power Plant to meet power needs.




