Maine Governor Vetoes Data Center Moratorium

The cleanest way to read Mills' veto is as a single-project decision dressed in statewide language. Her official statement does not contest the broad case for data center oversight; she signed L.D. 713's tax-incentive ban and announced an executive-order council to study siting in the same breath as the veto. What she would not accept was a moratorium that swept up the JGT2 / Sentinel project at the former Androscoggin Mill in Jay — a $550M redevelopment already under contract, partially permitted, and tied to a January 1, 2027 building-handover deadline. Mills had asked the legislature for a Jay-specific carve-out. When lawmakers refused to amend the bill to exempt one site, she vetoed the whole thing.

That sequence matters because it inverts the usual story about industry capture. There is no evidence in the record that the Data Center Coalition or Maine State Chamber of Commerce changed Mills' mind on the underlying policy — she still appears persuaded that statewide siting standards are needed. What changed her mind was a binding contract, a brownfield site in a town that lost its mill, and a developer (JGT2's Tony McDonald) who positioned the Jay facility as an existing-infrastructure reuse rather than a new hyperscale build. The veto is, functionally, a statement that one specific project's economics outweighed a first-in-nation regulatory framework that her own legislature had already passed with bipartisan margins. Whether that trade is defensible is the entire political question — and it is the question her override opponents are now organizing around.

Mills' official rationale leans hard on employment numbers: the Jay project, she wrote, would create 'more than 800 construction jobs' and 'at least 100 high-paying permanent jobs.' Those numbers are real, but the ratio is the part that drove the backlash. Construction jobs are by definition temporary; the permanent footprint is what a host community lives with for the asset's full operating life. And data centers are, post-construction, among the lowest-headcount industrial assets ever built — staffing densities of one employee per 10,000 to 50,000 square feet are common.

This is exactly the angle that dominated discussion on r/technology and r/Maine in the days surrounding the veto. The top-voted threads on the Bangor Daily News and Mother Jones links converged on a single critique: when politicians cite 'jobs' to defend data center subsidies and exemptions, they are mostly citing construction labor that vanishes the moment the building opens. State Sen. Tim Nangle had already framed the same tension in fiscal terms, pointing out that Maine's general fund struggles to cover health care and school funding while still finding subsidy room for 'the richest corporations.' L.D. 713, which Mills did sign, removes one piece of that subsidy stack by barring state business-development tax incentives for data centers — a partial concession that doesn't address the underlying employment-density argument but acknowledges the public's skepticism of the numbers.

L.D. 307's substantive policy concern was never primarily about jobs — it was about who pays for the transmission and generation buildout that a wave of 20+ MW data centers would force onto the New England grid. Sachs and the bill's coalition argued in public statements that without a coordinated siting framework Maine ratepayers would end up subsidizing infrastructure that exists primarily to serve out-of-state hyperscale operators and their AI workloads. The 13-member coordination council the bill would have stood up was supposed to deliver siting recommendations by February 1, 2027 — explicitly to answer the cost-allocation question before more projects landed.

Mills' veto leaves that question unanswered. The executive-order council she pledged in its place is a study body, not a permitting framework, and it does not bind future projects to wait on its findings. Meanwhile the Sentinel facility in Jay will move forward on its existing permit track, and any other 20+ MW project that files between now and a successful override (or a future legislative session) gets the same default treatment: project-by-project review and no statewide standard. Sachs' statement that the veto 'poses significant potential consequences for all ratepayers' is not rhetorical hyperbole — it is the precise structural critique the bill was written to address.

It is impossible to read this veto without the political backdrop: Mills is running for the U.S. Senate. NBC News flagged this framing in coverage of her position weeks before the veto. A high-profile decision that protects 800 construction jobs and a $550M private investment plays differently in a statewide general election than a moratorium that confronts the AI industry head-on, even one with strong grassroots support. Our Power's Seth Berry told reporters his five-year-old organization had 'never before seen an issue with such strong and bipartisan support as the data center moratorium' — and the bill's bipartisan passage in both chambers backs that up — but bipartisan support among engaged constituents and bipartisan support in a Senate primary are different audiences.

The political cost is now visible. Reaction within Maine-focused online communities skewed sharply negative across both energy-policy circles and the state's general-purpose subreddits, with one of the more-discussed threads written by a competing gubernatorial candidate explicitly attacking Mills. One political journalist's verdict on X — 'Mills just lost her primary' — captured how some observers framed the veto as a primary-defining moment rather than a routine policy disagreement. Food & Water Watch and Our Power are publicly calling for a legislative override, which would require a two-thirds supermajority in both chambers — a high bar even given the bill's original bipartisan margin, but a credible enough threat that the override math is now part of the post-veto news cycle. The political calculation that drove the veto may not survive the political reaction to it.

The reason this veto is national news rather than a Maine story is the timing. Good Jobs First counted more than 300 data center-related bills introduced across 30 states in just the first six weeks of 2026, with at least 12 in-session moratorium proposals modeled in part on the Maine framework. L.D. 307 was not just symbolic — it was the most procedurally advanced of any of them, the one most likely to actually become law. Its veto removes the precedent other state legislators were planning to cite.

The ripple is asymmetric. A successful Maine moratorium would have given moratorium sponsors in other states a working template, a roll-call record, and a sitting governor's signature to point to. A vetoed Maine moratorium gives the Data Center Coalition and its allied chambers of commerce something arguably more valuable: a high-profile case study in which a Democratic governor sided with a single $550M project over a bipartisan legislative supermajority. That is the version of the story Dan Diorio's coalition will be carrying into other statehouses for the rest of the 2026 session. Whether the override effort succeeds will determine which of those two narratives — 'even Maine couldn't get it through' versus 'Maine's legislature beat the industry anyway' — becomes the operative national talking point.