Skip to content
Infrastructure Accountability

New York Data Center Boom Needs Power Receipts, Not Blank-Check Subsidies

No paywall
10 sources
3,381 words
Pass

Listen
News Anchor voice
Ready when you are.



BadPD source-check, May 24, 2026: New York’s data-center fight just moved from local backlash into statewide ratepayer math. A May 24 Times Union investigation reports that proposed AI data centers across New York could collectively require electricity approaching the power demand of New York City, based on the paper’s review of New York Independent System Operator data. That is not a neighborhood zoning footnote. That is a grid-planning, tax-subsidy, water, environmental, and ratepayer-accountability story.

The biggest visible flashpoint is the proposed Stream Data Centers project at the Western New York Science, Technology and Advanced Manufacturing Park, known as STAMP, in the Town of Alabama in Genesee County. The Times Union reports Stream is seeking 500 megawatts of electricity, roughly one-third of the Capital Region’s power use. It also reports the project sits at a site where taxpayer funds were originally earmarked to launch a clean-energy manufacturing hub, including $56 million for infrastructure upgrades, before the earlier developer dropped out and a data-center proposal moved forward.

BadPD’s frame is not “ban all data centers.” The United States needs compute capacity, AI infrastructure, cloud capacity, and domestic digital infrastructure. The frame is also not “trust the developer and call it economic development.” If a data center wants city-scale power, public incentives, subsidized infrastructure, or special utility treatment, the public deserves the same thing before approval every time: power receipts, water receipts, tax receipts, ratepayer shields, and a build-it-right path.

What Is New

Times Union’s May 24 report links several strands that had been moving separately: proposed data-center loads in the NYISO queue, the Stream/STAMP fight in Genesee County, a statewide moratorium bill, Gov. Kathy Hochul’s opposition to an outright ban, and the Public Service Commission proceeding she launched to make large energy users pay their share of grid costs. The report says residents in Genesee County have swarmed public hearings and raised concerns about utility bills, water supplies, public health, tax breaks, and whether the project creates enough permanent jobs to justify the public support.

The report also quotes Hochul taking the lane BadPD has been pushing: New York should not be inhospitable to development, but it must make sure data centers are not creating a burden for ratepayers. That is the right policy doorway. The fight now is whether that doorway leads to enforceable tariffs, interconnection rules, water disclosures, subsidy clawbacks, and power-supply requirements, or whether it becomes another “we will study it later” lane while projects lock in.

Times Union reports that Stream would receive about $1.4 billion in subsidies from state and local tax exemptions, would spend roughly $20 billion on the facility, and says it would create about 120 permanent full-time jobs averaging $88,000. The county-side argument is that taxes on electricity, payments to local governments and schools, construction jobs, and payroll benefits make the project worthwhile locally. The counterargument is that state taxpayers, nearby residents, ratepayers, water users, and communities outside the host county may carry costs not fully reflected in the local benefit math.

The STAMP Receipts

GCEDC’s March 16 statement says Stream would build three 733,338-square-foot buildings on 90 acres that had already been rezoned for uses including data centers. GCEDC says Stream would use part of the electrical capacity approved for STAMP’s use by New York’s grid operator and argues the negotiated agreements would generate a direct financial benefit to the community that provides a 3-to-1 return.

GCEDC’s March 27 statement says it extended the written-comment deadline and scheduled another public hearing after technical limitations affected recording and livestreaming of a March 19 hearing. That matters. If the public hearing on a massive power user cannot be recorded and livestreamed properly, the fix cannot be “too bad, moving on.” The fix is exactly what GCEDC said it would do: extend comment time, hold another hearing, and keep project documents available for public review.

GCEDC also argues STAMP is already benefiting town residents, including through public water funding, road improvements, and services. That claim belongs in the article because the public needs both sides. A project can bring revenue and infrastructure. It can also create ratepayer, water, environmental, noise, land-use, and opportunity-cost problems. The public should not be forced to choose between booster math and panic math. It should get the actual math.

Stream’s own project page says the company is exploring a data-center campus at STAMP and expects hundreds of construction and trade jobs during development and more than 120 long-term full-time jobs once operational. Stream emphasizes responsible design, operational excellence, long-term investment, environmental compatibility, workforce quality, regional infrastructure, and community partnership. Those are useful promises. They are not receipts until they are matched to binding project terms, public utility filings, water plans, construction permits, tariff treatment, and enforceable community obligations.

The Statewide Power Problem

Gov. Hochul’s February 12 PSC announcement is the official state control record. The governor’s office said the PSC opened a proceeding to advance the Energize NY Development initiative, reviewing interconnection processes, cost-allocation mechanisms, and tariff structures for integrating large loads with the state’s transmission and distribution systems. The stated goal is to support economic development without hurting ratepayers.

The same release says New York will enforce a simple standard: large data-growth industries must cover the utility costs of expansion the way ordinary consumers do. It also says that if they do not pay more, they must supply their own energy. That line should be stapled to every data-center hearing in the state. Bring your own power is not anti-compute. It is how pro-compute policy avoids turning residential bills into an invisible subsidy.

The governor’s office said that as of January 2026, the NYISO interconnection queue included 48 projects representing more than 11 gigawatts of new large load, with many related to energy-intensive industries such as data centers. The release warned that large loads can impose costs on ratepayers through interconnection upgrades and impacts on reliability and electric supply, and that saturated queues make system planning harder when it is unclear which projects are real.

That is the accountability center of the story. The public needs to know which projects are serious, which are speculative, which have site control, which have a power-supply plan, which depend on subsidized hydropower or public infrastructure, which will require transmission or substation upgrades, and which will pay if a project disappears after the grid has already spent money preparing for it.

Moratorium Or Build-It-Right Rules?

The New York Senate’s May 15 AI Week release says Senator Kristen Gonzalez co-prime sponsors a bill with Senator Liz Krueger and Assemblymember Anna Kelles to create a three-year moratorium on data-center permits in New York. The release says advocates rallied for a pause to give the state time to address high energy demand, unfair utility-rate hikes, fresh water use, noise pollution, and other environmental impacts. It also says New York has surpassed 130 operational data centers.

DLA Piper’s legal summary identifies Senate Bill S.9144 as a proposal to impose a statewide moratorium of at least three years on state or local permits for data centers capable of using 20 megawatts or more, until DEC and PSC actions are complete. That is a serious threshold. Twenty megawatts is large enough to capture major AI and cloud infrastructure, but also broad enough to create real questions about whether New York would freeze potentially responsible projects along with irresponsible ones.

BadPD’s read is that a pause can be responsible if it buys time for enforceable standards. A pause becomes weak policy if it stops projects without publishing the rules for a compliant one. The state should not approve blank-check projects. It also should not create a vague anti-compute bottleneck that pushes capacity elsewhere, raises costs, and leaves ordinary users paying for scarcity through cloud prices, hosting prices, subscription prices, device lock-in, and more aggressive data monetization.

The better standard is boring because boring is enforceable: classify projects by load, cooling method, water demand, backup generation, grid-impact profile, emissions profile, noise profile, local benefit, tax benefit, and resident exposure. Let projects that bring their own clean firm power, avoid cheap public water, use waterless or closed-loop cooling where feasible, support the grid, pay for upgrades, disclose backup emissions, and accept enforceable local conditions move faster. Slow or reject projects that cannot produce those receipts.

The Subsidy Problem

Times Union reports the Stream project would receive about $1.4 billion in subsidies from state and local tax exemptions. Investigative Post has been warning for months that the STAMP subsidy package and IDA structure need hard scrutiny. Its January and February reporting framed the Genesee County IDA as both project promoter and party that can benefit from STAMP development, while critics including the Tonawanda Seneca Nation and other opponents raised environmental, sovereignty, process, and subsidy concerns.

BadPD is not treating advocacy groups, Investigative Post, GCEDC, Stream, Hochul, or the Times Union as final authority. Each is a receipt. The question is whether they can be reconciled. If GCEDC says the project produces a 3-to-1 return, publish the full model, assumptions, discount rates, beneficiaries, and who is excluded. If opponents say state taxpayers lose while local governments gain, publish the state-versus-local cost split. If Stream says it will not raise electricity prices, publish the tariff treatment, interconnection-cost allocation, power-purchase strategy, and risk if the company or tenant leaves.

A subsidy can be justified. A subsidy can also become a transfer from public ratepayers and taxpayers to a private infrastructure customer that creates relatively few permanent jobs. The difference is not rhetoric. The difference is a public ledger.

Water, Cooling, And Land

New York’s fight is mostly framed around electricity, but water belongs in the same file. Data centers can use water for evaporative cooling, humidification, domestic use, fire protection, commissioning, maintenance, and emergency operations. Some modern designs use closed-loop, dry, or waterless cooling, but the public cannot verify that from a glossy project page. The project should disclose cooling technology, expected gallons per day, peak draw, source water, wastewater handling, chemical treatment, drought operations, and emergency fire-water requirements.

Times Union reports residents near the Stream proposal cite water supplies, public health, utility bills, and agriculture as concerns, while officials say some fears are overstated. That split is normal in data-center fights. The way through it is records, not eye-rolling. If the project has office-building-scale water impact, publish the engineering basis. If it has closed-loop cooling, publish fill/refill cycles and blowdown assumptions. If it needs no meaningful process water, make that a binding permit condition.

Land also matters. STAMP was pitched around science, technology, advanced manufacturing, and clean energy. Times Union reports the site received public infrastructure support for a clean-energy manufacturing vision before a data-center use advanced after a developer dropped out. A data center may be a lawful and economically valuable use. But when a site receives public money under one promise and later shifts to a lower-job, high-load use, the public deserves a fresh benefit test.

Confirmed, Alleged, Pending, Disputed

Confirmed: Times Union published a May 24 statewide data-center report. Stream is proposing a large data-center campus at STAMP in Genesee County. GCEDC has publicly defended the project and the proposed agreements. Hochul’s PSC proceeding is active as an official state policy lane. The governor’s February release says NYISO had more than 11 GW of new large load in the queue as of January 2026. New York lawmakers have introduced or promoted a three-year data-center moratorium bill. Stream’s own project page describes 120+ long-term full-time jobs and a multi-year construction phase.

Reported and developing: Times Union reports the Stream/STAMP project is seeking 500 MW, would receive about $1.4 billion in subsidies, would spend roughly $20 billion, and would create about 120 permanent full-time jobs. Times Union also reports proposed data-center loads statewide could approach New York City-scale electricity demand. These figures should be checked against NYISO queue records, final project applications, incentive agreements, and PSC filings.

Alleged or advocacy-framed: opponents say the project could raise utility costs, harm water resources, degrade public health, damage agriculture, and misuse public incentives. GCEDC and Stream say many concerns are overstated and that the project will bring major local benefits. Food & Water Watch, NY lawmakers, and allied advocates support a pause or moratorium; Hochul says she opposes an outright ban and prefers ratepayer-protection rules.

Pending: final PSC tariff/cost-allocation rules; the full Stream/STAMP interconnection treatment; final incentive agreements; public water/cooling disclosures; backup-power and emissions plans; NYPA/ReCharge NY power-allocation details; state-versus-local benefit accounting; community benefit obligations; clawbacks if promised jobs or payments fail; and whether S.9144/A.10141 or a narrower cost-accountability bill advances.

BadPD Standard For New York

New York should not hand data centers a blank check. It also should not let an anti-compute reflex become the whole policy. The state can do the harder thing: write a build-it-right path that protects residents and still builds needed digital infrastructure.

The minimum package should include: bring-your-own-power or pay-your-full-cost tariffs; no stranded-cost dumping on existing ratepayers; public interconnection studies; demand-response obligations where technically feasible; grid-support or battery-storage commitments; water-source and cooling-method disclosures; waterless, dry, closed-loop, or reclaimed-water preference where watersheds demand it; backup-generation emissions limits; noise and heat-rejection standards; tax-benefit transparency; local and state benefit accounting; public comment windows that actually work; and enforceable clawbacks.

If a project can meet that standard, it should be able to move. If it cannot, the public should not subsidize it and then be told the electricity bill, water pressure, noise, diesel backup, or tax exposure was unavoidable. Data centers are not magic. They are industrial infrastructure. Treat them that way.

This deserves full-post treatment because the New York file now has all the ingredients BadPD tracks: statewide grid exposure, public subsidies, resident-cost risk, a specific 500 MW project, official PSC action, a moratorium proposal, and a governor trying to split the difference between economic development and ratepayer protection. The next update should be document-heavy: NYISO queue entries, PSC docket filings, GCEDC incentive agreements, NYPA power allocations, Stream water/cooling commitments, and the actual legislative text moving in Albany.

Source Trail

BadPD source repair: what this page can prove

This article has been upgraded from a fast watcher item into a clearer receipt ledger for New York Data Center Boom Needs Power Receipts, Not Blank-Check Subsidies. The original item remains above. This repair section does not add a verdict. It explains what the attached source trail can support, what it cannot support by itself, and what records would make the story stronger.

The topic lane is Infrastructure Accountability. BadPD is treating www.timesunion.com, www.governor.ny.gov, www.gcedc.com, www.streamdatacenters.com, www.nysenate.gov, www.dlapiper.com, www.investigativepost.org, www.foodandwaterwatch.org as receipts, not as final authority. A receipt can prove that a claim was made, that an agency published a statement, that a news outlet reported a fact, or that a public dispute exists. A receipt does not automatically prove the whole story. That is why this page keeps the links visible and keeps the open questions attached.

Source ledger

What is confirmed right now

The page confirms that BadPD captured a public source trail around this claim and preserved the lead item with supporting checks. It also confirms the publication context, the source lane, and the follow-up direction. If the attached links disagree, the disagreement is part of the story. If they agree only on the existence of a claim, then the claim still needs stronger records before it should be treated as settled fact.

For readers, the useful value is the source map. It shows where the first claim came from, where the cross-checks came from, and which public institutions or publishers are part of the record. That matters because low-quality news often strips the claim away from its paper trail. BadPD keeps the paper trail close to the claim so the reader can test it.

What is not proved yet

This page should not be read as proof of every allegation, quote, motive, number, or timeline in the wider dispute. It should be read as a live accountability record. The strongest next version would add primary documents, direct video, court filings, official transcripts, public-meeting records, procurement records, agency data, or named on-the-record responses from the people and institutions involved.

Questions BadPD still wants answered

  • What public permits, utility filings, water agreements, power contracts, tax incentives, zoning votes, and meeting minutes exist?
  • Who pays if the project needs more grid capacity, emergency backup power, road work, water capacity, or wastewater handling?
  • Does the proposal bring its own power, closed-loop cooling, leak detection, public reporting, and enforceable local conditions?
  • Which claims come from residents, which come from government records, and which come from advocacy or industry messaging?

Why this stays on BadPD

BadPD covers stories where power, public money, police authority, courts, public safety, infrastructure, recalls, war powers, or public records are in play. A story does not need to be finished to deserve tracking. But it does need a clear label. This page is now labeled as a source-ledger item unless and until the record supports a stronger long-form conclusion.

The standard from here is simple. If a stronger record appears, this post should be updated with the new receipt and the claim should move from pending to confirmed, disputed, or corrected. If no stronger record appears, the post should stay cautious. That is the difference between accountability coverage and content churn.

Tips + Corrections

Send receipts for the desk to research

Send corrections, missing records, police-accountability tips, good-cop public-service receipts, government/court/war leads, recall alerts, or property-tax help resources. Tips are leads only until BadPD verifies records.

What helps
Links, dates, agency names, docket numbers, bodycam IDs, recall numbers, forms, and official pages.
How we treat it
Every tip is a lead, not a fact. The desk checks records before publishing.
Advertising
Use advertising inquiry when you want clearly labeled sponsor space or available ad placements on BadPD.