Tag: Data Center Moratorium

  • Montgomery’s 6-Month Pause Shows a Retired Power Plant Won’t Fast-Track a Data Center

    Montgomery’s 6-Month Pause Shows a Retired Power Plant Won’t Fast-Track a Data Center

    TL;DR · 30-second read

    The Short Version

    Montgomery County, Maryland, a large suburb just outside Washington, has stopped accepting building applications for new data centers for six months. Data centers are the huge warehouses of computers that run apps, online storage and artificial intelligence.

    The surprise is that the pause also covers a project already proposed on the site of an old, shut-down power plant. Builders often like those sites because they are already wired into the electric grid.

    Local leaders say they want rules on electricity, water and noise written before anything gets built.

    On June 12, 2026, Montgomery County Executive Marc Elrich signed an executive order directing the county’s Department of Permitting Services to stop accepting, processing and considering permit applications for new data centers. Montgomery County announced that the order takes effect immediately and sets a six-month moratorium, which can end sooner if the County Council adopts permanent zoning rules for data centers.

    The pause applies to projects already proposed, including a potential data center at the site of the decommissioned power plant in Dickerson, in the county’s western reaches along the Potomac River. Council Vice President Marilyn Balcombe and Councilmembers Will Jawando and Kristin Mink backed the order.

    Executive Summary

    Montgomery County has frozen data center permitting for six months so its County Council can write a legal framework for the industry. The county said the order responds to concerns about data centers’ energy consumption, water use for cooling, and noise near homes. It is a pause, not a ban: officials described it as time to set rules before applications move forward.

    What makes the order consequential is its scope. Elrich said his approach differs from an earlier proposal by Council Member Glass that would have exempted the Dickerson site and let it keep moving through permitting. His order does not exempt it. A project on a retired power plant parcel, which is the kind of site developers typically prize for its existing grid ties, now waits in the same line as everything else.

    For developers and investors, the signal is that in Montgomery County, a site’s power-plant legacy is not a substitute for local approval. The rules that emerge on clean energy, water, noise and labor will determine whether the county remains a practical option next to one of the world’s densest data center markets.

    Why a Retired Power Plant Didn’t Earn a Head Start

    For data center developers, a decommissioned power plant is often one of the most attractive parcels available. Such sites are usually already used for heavy industry, and they sit where high-voltage transmission lines once carried the plant’s output to the grid. That matters because the scarce input for today’s AI-driven data center buildout is electricity, not land. Connecting a large new electricity customer can take years, and a site with an existing grid footprint is widely seen as a way to shorten that wait.

    Montgomery County’s order removes that advantage for Dickerson. Elrich explicitly contrasted his order with Council Member Glass’s earlier proposal, which exempted the Dickerson site. Councilmember Mink said a large data center is in the permitting process now and that the order covers it “and all others,” calling that an important distinction. Councilmember Jawando said the moratorium bill he introduced in May was the only one that covered the Dickerson project. The county’s elected leadership treated the site’s history as no reason to let it proceed ahead of the rules.

    The reasoning is visible in the concerns officials named: grid strain, brownouts, water for cooling, noise, and watershed protection. An existing transmission connection addresses whether power can physically reach a site. It does not answer whether the county wants that load on its local system, where cooling water comes from, or how loud cooling equipment will be near homes. The Dickerson developer is the first party affected. The same logic applies to any developer or landowner that has valued retired generating sites on the assumption that local approval follows the grid connection. In Montgomery County, at least, it does not.

    What Six Months Is Meant to Produce

    The moratorium is scheduled to expire in six months, around mid-December 2026. It ends earlier if the County Council adopts Zoning Text Amendments, which are changes to the written zoning code that define where a use is allowed and under what conditions. In practice, the pause gives the Council a deadline. If permanent rules arrive first, the freeze lifts on them.

    Officials have already sketched what they want those rules to cover. Jawando listed “clean energy, no subsidies, union labor, and a safe watershed.” Mink wants the County Noise Ordinance updated and watershed protections established. Climate Change Officer Sarah Kogel-Smucker said the goal is to align data center development with the county’s climate goals through best practices for clean energy and efficient cooling. Each of these would raise a project’s costs or narrow its design choices. Clean-energy requirements affect how a facility buys power. Water limits push operators toward cooling systems that use less water, which can mean more electricity. A no-subsidy stance removes the tax incentives many jurisdictions use to compete for these projects.

    None of these positions has become law yet, and they will not all carry equal weight. How the Council balances them will decide whether Montgomery becomes a place where data centers can be built under strict conditions or one where the conditions make the economics hard to close. Balcombe framed the intent as the former: “The moratorium does not mean we stop; it means we work harder.”

    A Pause on the Doorstep of Data Center Alley

    Montgomery County sits across the Potomac River from Loudoun County, Virginia, whose Ashburn area is known as Data Center Alley and hosts one of the largest concentrations of data centers in the world. Maryland and Northern Virginia are both served by PJM Interconnection, the grid operator for much of the mid-Atlantic. That is why concerns about grid strain and brownouts carry weight on both sides of the river.

    The order should not be read as more than it is. It is one county’s six-month pause, and it does not by itself redirect regional demand. What it does show is that a jurisdiction immediately adjacent to the industry’s busiest cluster has chosen to write rules before approving projects, including one on a site with an energy-industry past. Jawando cast the decision in national terms, saying communities across the country face the same choice. Developers looking for land near Northern Virginia’s network and power infrastructure now have one fewer county where timing is predictable.

    Weighing the Claims on Both Sides

    The order’s stated rationale includes serious claims, notably brownouts. Whether any single facility would contribute to them depends on its size and on the utility’s planning, and officials framed the risks in general terms rather than attaching load or water figures to the Dickerson project. The rules the Council writes will be more durable if they rest on measured impacts rather than on the general reputation of the industry.

    The same scrutiny applies to the other side of the argument. Jawando’s description of “corporate promises of profits that may never come” is a political judgment, not a finding. Kogel-Smucker’s observation that data centers are “critical to our digital economy” is the counterweight. No jobs, tax revenue or investment figures for the Dickerson project were offered at the announcement to test either view. The six months are most useful if both the county and the developer put those numbers on the table.

    Background

    Montgomery County is a large suburban county bordering Washington, D.C., to the northwest, with its western edge on the Potomac River. Across the river lies Loudoun County, Virginia, home to Ashburn’s Data Center Alley, one of the largest concentrations of data centers anywhere. Data center demand across the region has grown with cloud computing and, more recently, artificial intelligence workloads, which require large amounts of electricity and cooling.

    Montgomery County had been working toward data center rules before the order. Its Climate Change Officer co-led a community forum on data centers in February 2026, Council Member Glass had put forward a proposal that exempted the Dickerson site, and Councilmember Jawando introduced a moratorium bill in May that covered Dickerson. Elrich’s June 12 executive order paused permitting while the Council finishes that work.

    Sources

    Source: Montgomery County Executive Marc Elrich Signs Executive Order to Temporarily Pause Data Center Permitting — Montgomery County, Maryland’s announcement of a six-month moratorium on data center permit applications, including the proposed Dickerson project.

  • Louisville’s 500,000 Sq Ft Cap Shows Local Zoning Now Gates AI Data Center Scale

    Louisville’s 500,000 Sq Ft Cap Shows Local Zoning Now Gates AI Data Center Scale

    TL;DR · 30-second read

    The Short Version

    Kentucky’s two biggest cities are drawing lines around the giant computer warehouses being built to run artificial intelligence.

    Louisville proposed a size limit of 500,000 square feet, roughly nine football fields. Only three months earlier, the city approved one about 28 football fields big. Lexington stopped accepting new applications until October 31 after neighbors objected to plans to expand one.

    Why it matters: city halls, not just tech companies, are now deciding how big these buildings can get and where they can go.

    Kentucky’s two largest cities moved on June 9 to rein in hyperscale data centers, the Kentucky Lantern reported. Lexington’s Urban County Council suspended its legislative rules to impose a moratorium on data center applications through Oct. 31 while it writes zoning amendments. The same day, the Louisville Metro Planning Commission released a draft ordinance that would ban any data center larger than 500,000 square feet and restrict facilities over 250,000 square feet to industrial areas.

    Louisville residents have 30 days to comment on the draft before it goes to Louisville Metro Council. In March, the same planning commission approved a 1.6 million-square-foot data center in West Louisville despite local opposition.

    Executive Summary

    Lexington and Louisville took different routes to the same goal on the same afternoon. Lexington hit pause: no new data center applications until Oct. 31, prompted by a developer’s purchase of a local data center property that it intends to expand. Louisville went straight to rules: a draft siting ordinance with a hard size ceiling of 500,000 square feet and industrial-only zoning for anything over 250,000 square feet.

    The significance lies in the numbers. Louisville’s proposed ceiling is less than a third of the size of the facility the city approved three months earlier. For developers planning large AI campuses, that means the maximum scale of a project in Kentucky’s biggest city may be fixed by a planning document, regardless of what the grid or the supply chain could support.

    Both cities cited resident concern. Lexington Mayor Linda Gorton said she supports “very tight controls” and that the city does not support public incentives for the developer seeking to expand.

    A Ceiling Set Below a Third of March’s Approval

    The number that carries this story is the gap between two Louisville decisions made three months apart. In March, the Louisville Metro Planning Commission approved a 1.6 million-square-foot data center in West Louisville over local objections. On June 9, the same commission released a draft ordinance that would ban any data center larger than 500,000 square feet, less than a third of that approved facility, and confine anything over 250,000 square feet to industrial zones.

    This is how local zoning becomes a constraint on the scale of AI buildout. Hyperscale campuses, the very large facilities built for cloud and AI operators, draw much of their economic advantage from concentration: one site, one large electrical connection, one security perimeter, shared cooling infrastructure. A hard floor-area ceiling means a developer who wants that scale in Louisville would have to split it across buildings or sites, if the final ordinance allows that at all, or build somewhere else. In either case, the largest permissible project is being set by the planning code, independent of what power and equipment supply could support.

    The effects fall on specific groups: developers and landowners holding Louisville sites, the local utility planning for large new electrical loads, and residents who opposed the March approval. Brian Davis, director of Louisville’s office of planning, described the goal as “clear, achievable standards that provide transparency and clarity for both residents and potential developers.” Clarity does have value for investors, since a known ceiling is easier to finance around than a case-by-case fight. But the ceiling sits well below the size of the projects that prompted it.

    Two Cities, Two Tools: Pause Versus Rulebook

    Lexington and Louisville used different instruments on the same day. Lexington’s council suspended its legislative rules to impose a moratorium through Oct. 31 while it drafts zoning amendments: pause first, rules later. Louisville, where a separate committee tabled a data center moratorium earlier in June, went straight to draft regulations and opened a 30-day public comment period before the ordinance reaches Metro Council.

    For developers, the difference matters. A moratorium stops the clock entirely and leaves the eventual rules unknown. Lexington’s amendments could end in controls or, potentially, an outright ban. A draft ordinance keeps applications possible and tells the market roughly what it will face. Neither city has final rules today, and Lexington’s pause alone runs for nearly five months.

    Lexington’s action was triggered by a single transaction, a developer buying an existing local data center property with plans to expand it. Council member Emma Curtis called it “a case of an issue being expedited because of constituent concern and advocacy.” That is a direct statement that resident objections, not a staff study, set the timetable. That is a legitimate part of local democracy. It also means the rules will be written with one specific project in view.

    Square Feet Are a Blunt Proxy for the Grid

    Mayor Gorton stated the concern most clearly: data centers “do not produce many jobs, and have the potential to increase utility costs on local residents.” Both points are common in these debates, and both deserve the same scrutiny applied to developers’ promises of economic benefit. Gorton did not attach figures to either claim. Whether a large facility actually raises household bills depends heavily on how the utility and state regulators assign the cost of new generation and transmission, and neither city’s action settles that question.

    That exposes a limit in Louisville’s approach. Floor area is easy to measure and enforce, but it is only an indirect measure of what worries residents most: electricity demand. Servers built for AI draw far more power per rack than conventional cloud equipment, so two buildings of the same size can place very different loads on the grid. A 500,000-square-foot cap controls land use, traffic and physical footprint. It controls power draw only loosely.

    For industry readers, the practical point is that Kentucky’s largest cities are regulating the most visible dimension of data centers first. Site selection now depends on local square-footage thresholds as well as power availability and land cost, and Louisville’s shift between March and June shows those thresholds can move within a single planning cycle.

    Background

    Kentucky has long hosted smaller data centers supporting services such as cloud storage. The wave of investment in artificial intelligence has brought a different class of facility nationwide: hyperscale data centers that can consume as much electricity as an entire power plant and can span millions of square feet.

    Louisville has already experienced that shift. In March its Planning Commission approved a 1.6 million-square-foot data center in West Louisville despite local pushback, and earlier in June a separate city committee tabled a proposed data center moratorium. Lexington’s action followed a developer’s purchase of an existing local data center property with plans to expand it.

    Sources

    Source: Kentucky’s two largest cities take action to address concerns over hyperscale data centers (Kentucky Lantern), on Lexington’s data center moratorium and Louisville’s draft data center siting ordinance.

  • Seattle’s 369 MW Data Center Freeze Shows Why AI Load Needs Ratepayer Buy-In

    Seattle’s 369 MW Data Center Freeze Shows Why AI Load Needs Ratepayer Buy-In

    TL;DR · 30-second read

    The Short Version

    Seattle’s city council voted unanimously on June 9 to temporarily stop new giant data centers from being built in the city. Data centers are warehouse-sized buildings packed with computers, and the biggest new ones run artificial intelligence.

    Four companies had asked the city’s electric utility to power five of them. Together, those five could draw as much electricity as about 300,000 homes.

    Council members said their main worry is that everyone else’s power bills could rise to cover the cost. The pause gives the city time to study bills, water use and pollution before it makes any permanent decision.

    On June 9, 2026, the Seattle City Council unanimously adopted two measures aimed at large data centers, the council announced on its official blog. Amended Council Bill 121214, sponsored by Councilmember Eddie Lin and Council President Joy Hollingsworth, places an emergency, temporary freeze on siting new data centers while the city conducts impact studies. The freeze covers facilities used primarily for storing and processing digital data that have more than 20 megavolt-amperes (MVA) of power capacity and require uninterruptible power. It can be extended by six months if necessary.

    A companion measure, amended Resolution 32204 sponsored by Councilmember Debora Juarez, sets a policy framework and directs city departments and the Mayor’s Office to analyze how such facilities affect grid capacity, water use, utility rates, land use, local jobs and public health. The votes followed reports in April that four companies had approached Seattle City Light, the city’s electric utility, about five large data centers with a combined maximum demand of 369 megawatts. Mayor Katie B. Wilson said the mayor’s office looks forward to signing the ordinance, which takes effect immediately under its emergency designation. A public hearing is required within 60 days.

    Executive Summary

    Seattle has paused new large data centers after four companies sought 369 megawatts of capacity for five facilities. By the council’s own comparison, that is enough electricity to power about 300,000 homes. The ordinance uses a 20 MVA threshold, which targets large, always-on computing facilities rather than small server rooms. It takes effect immediately, and the council says it can be extended by six months.

    The notable part is the reason. Every official quoted — the two sponsors, the council president and the mayor — cited utility rates or ratepayers. Environmental and water concerns were also named, but the shared argument was cost. The question the council put to developers is not whether the grid can physically deliver the power. It is who pays to deliver it.

    For AI infrastructure developers, the lesson reaches beyond Seattle. Where the people who govern a utility answer to the people who pay its bills, a large new load has to make a persuasive case to those ratepayers. A service request alone may not be enough.

    The Argument That Carried the Vote Was the Power Bill

    The measures passed 9-0, and the officials behind them made a consistent case. Councilmember Lin said large AI data centers are “driving up utility costs for residents and small businesses” and that “Seattleites should not be subsidizing record profits of large corporations from the AI boom.” Council President Hollingsworth said growth must not come “at the expense of residents and ratepayers.” Mayor Wilson cited “the potential impacts of large-load data centers on utility rates.” Air, water and noise concerns appear alongside, but rates are the thread that runs through every statement.

    Here is the mechanism. When a utility has to add substations, transmission lines or new power supply to serve a single very large customer, its rate design decides who pays. If those costs are spread across the whole customer base, households and small businesses carry part of them. If the tariff assigns them to the new load, the developer carries them. Resolution 32204 directs the city to study exactly these questions, grid capacity and utility rates, before any permanent rules are set. In Seattle the utility is City Light. It sits under the same elected council that voted the pause, and Juarez chairs the committee that oversees it. The people deciding whether 369 megawatts gets connected are directly accountable to the people who would share the bill.

    That is why this matters for AI infrastructure. A developer can secure land, chips and a utility service request and still be stopped at the point where the grid-upgrade bill meets ratepayers. The council has not yet shown Seattle-specific evidence that these five projects would raise rates; producing that evidence is the stated purpose of the studies. The vote still establishes the test. A large AI load in this city will have to show residents it will not cost them money. Developers who can answer that question credibly, for example by paying their own grid costs, will be better placed than those who cannot.

    What 369 Megawatts Means for a City Grid

    The five proposed facilities had a combined maximum demand of 369 megawatts, about 74 megawatts each on average. The actual split among them has not been disclosed. Maximum demand is peak draw, not average use. However, large computing facilities tend to run close to their peak around the clock, which makes them attractive customers for utility revenue and demanding ones for utility planning. The council’s comparison to roughly 300,000 homes shows the scale: this is a city-sized block of new demand, requested by four companies in a single round.

    The 20 MVA threshold sets the boundary. Megavolt-amperes measure electrical capacity and, for data center equipment, are close to megawatts. The definition also requires uninterruptible power, meaning battery and backup systems that keep servers running through outages. Together these criteria capture purpose-built, high-density computing sites while leaving smaller office server rooms outside the definition.

    Colocation Stays, Mega-Sites Wait

    Lin drew an explicit line between “mega AI data centers” and the city’s smaller colocation facilities. Colocation facilities are shared buildings where many organizations rent space for their servers, and Lin said Seattle’s support 911 call centers, municipal operations, hospitals, universities and cancer research. The freeze applies to new siting, so existing facilities keep operating. The open question for colocation operators is how the 20 MVA line will apply to any expansion plans.

    Where the demand goes next is uncertain. Lin spoke of developing safeguards “locally and regionally,” which suggests the city expects the issue to extend beyond its borders. Developers could wait out the studies, redesign projects to meet whatever conditions emerge, or pursue sites elsewhere in the region. None has said publicly which it intends.

    What the Pause Does and Does Not Establish

    Juarez described the measure as a pause for accountability and said it “does not stop AI or data centers.” It is temporary, it requires a public hearing within 60 days, and permanent rules depend on studies that have not yet been done. The council cited “tens of thousands” of residents raising concerns and pointed to rate increases elsewhere in the country. Both are statements of position; the studies are what will test them locally. The developers’ side is equally unsubstantiated so far. The four companies have not publicly set out what they would pay for, what jobs or tax revenue they would bring, or how they would limit the impact on existing customers.

    This is one city’s decision, and it should not be read as a nationwide trend. It is notable because Seattle is a major West Coast technology center, and because the council framed the decision in cost terms rather than opposition to the technology itself. That framing can be answered with evidence, which gives both sides a clear question to argue over.

    Background

    Seattle City Light is the city’s electric utility, and the elected City Council oversees it through a committee currently chaired by Councilmember Debora Juarez. That structure puts decisions about serving very large new customers in the hands of officials who answer directly to local voters and ratepayers.

    Large data centers, especially those built for artificial intelligence, need continuous, high-capacity power, and they have become a growing source of new electricity demand for utilities across the United States. Seattle’s action came two months after reports that four companies had approached City Light about five facilities. Seattle’s decision is one of the more prominent local responses to that growth, because the city is a major West Coast technology center.

    Sources

    Source: City Council passes emergency data center moratorium and policy framework, Seattle City Council Blog, June 9, 2026: the council’s announcement of Council Bill 121214 and Resolution 32204.

  • A Nebraska County’s 1-Year Data Center Pause Shows AI Builds Now Hinge on Zoning

    A Nebraska County’s 1-Year Data Center Pause Shows AI Builds Now Hinge on Zoning

    TL;DR · 30-second read

    The Short Version

    A farm county in southeast Nebraska has put new data centers on hold for up to a year. Data centers are the huge warehouse-like buildings full of computers that run artificial intelligence.

    Residents were alarmed by reports of a Google plan for a Nebraska facility that could use more than three times the electricity of the entire city of Lincoln on a hot summer day. They asked about water, power bills and heat.

    A new state law now gives counties a deadline to rule on some projects. Counties without rules may pause first and write rules later.

    The Otoe County Board of Commissioners in southeast Nebraska voted on Tuesday, May 19, to suspend the permits needed for a new data center for up to a year, Nebraska Public Media reported, carrying reporting by the Flatwater Free Press. Commissioner Chuck Cole said the pause is meant to give county officials time to study the issue and update county regulations.

    The vote followed local concern about a Google proposal for a large Nebraska data center. According to documents shared at a private utility meeting in January, that facility could require more than triple the electricity the city of Lincoln uses during its hottest months. The proposal did not name a site. The Omaha-based energy developer Tenaska, described as a potential partner, has optioned large tracts of land in southeast Nebraska, including in Otoe and Gage counties. Gage County’s planning and zoning commission is scheduled to hold a hearing on its own moratorium in June.

    Executive Summary

    Otoe County has not rejected data centers. It has stopped issuing the permits for one while it writes rules it does not yet have. That distinction matters to anyone planning large AI facilities in rural America. The practical obstacle in Otoe is not a lack of electricity or land. It is the absence of a local rulebook that can answer residents’ questions about water, power costs and heat before a project arrives.

    Two new Nebraska laws raise the stakes. One allows private power plants built to serve a single large industrial customer to connect to the grid. That law is widely seen as aimed at data centers and was backed by Tenaska’s CEO at a legislative hearing. The other law requires counties to rule on some projects within a fixed period. Jon Cannon of the Nebraska Association of County Officials said that deadline may prompt counties to adopt moratoriums first so they are not forced to rule without regulations in place.

    Otoe is one of several signals. Madison County now requires a special permit for data centers, Gage County is weighing a pause, and, according to the report, at least 14 states have considered statewide moratoriums this year.

    A Pause to Write Rules, Not a Permanent No

    A moratorium is a temporary halt on a category of approvals. Otoe’s suspends data center permits for up to a year. The board framed it as time to study the issue and update its regulations, not as a verdict on the industry. Wynee Benedict, one of the residents who pushed for it, described the goal in regulatory terms: “We needed regulations on the books prior to a data center coming to this county. We don’t want to have to play catch up and regulate something that’s already here.”

    Residents did not all agree. Jim Nemec supported time to study the issue but warned about the signal it sends: “Are we sending out the impression that business is closed here?” That is a fair concern. A county that pauses without a clear end date, or that uses the year to write rules nobody can meet, risks becoming a place developers skip. A county that uses the year to publish clear standards on water, noise, setbacks and power costs may become an easier place to build than one with no rules at all. Setbacks are required distances from homes or roads. The ordinance the county drafts will matter more than the vote itself.

    Why AI Siting Now Runs Through the County Board

    This is the core of the story. The scale being discussed in southeast Nebraska is large. The Google proposal could require more than triple Lincoln’s summer electricity use, and the organizers in Gage County said they understood it would include a private natural gas plant. At that size, a project needs the grid connection, the generation, the land and the local land-use permit. The state has now eased the power question by allowing private generation dedicated to a large customer. Tenaska has reportedly secured land options, which are contracts giving it the right to buy or lease land later. The piece still in doubt is the county permit, and in Otoe that piece is now frozen for up to a year.

    The state’s new decision-deadline law pushes counties in the same direction. It was intended to stop counties from stalling projects indefinitely. But a county with no data center rules that faces a firm deadline to decide on an application has two choices: rule without standards, or pause until it has them. Cannon expects many to pause, and not only for data centers. For developers this matters a great deal. A law designed to shorten approvals could lengthen them in counties that are not ready, and in the short term the counties that are not ready are most of the rural counties where land and gas access make these projects attractive.

    This should not be overstated. One county’s vote is not a statewide trend, and Cannon himself said attitudes will vary from county to county, as they have for wind and solar. But Otoe, Madison and Gage have all acted or scheduled action within weeks of each other, and all three are responding to the same prospect. That points to county zoning as the next checkpoint for rural AI campuses, alongside power and fiber.

    Power Was Handled in Lincoln; Water Was Left to the Counties

    Nebraska’s legislature and Gov. Jim Pillen addressed the energy question directly. The private-generation law is meant to keep large new loads from burdening existing ratepayers. Virginia shows what happens when this goes unaddressed. Joe Lerch of the Virginia Association of Counties said the state’s main utility has had to postpone connecting some new data centers for lack of power and transmission capacity.

    Water got no equivalent state-level answer, and in Otoe and Gage it is the concern residents raise first. Gage County organizer Anna Wolken said the top issue would be water, because both a gas plant and a data center can draw on it. Gas plants use water for cooling, and many data centers use water to carry heat away from their servers. How much depends heavily on the cooling design. Air-based and closed-loop systems use far less than evaporative ones. Nobody involved has said publicly which approach the proposed facility would use.

    A separate transparency law will require data centers to report their owners, size, location, annual electricity demand, water use and tax incentives each year. That gives county officials comparable data for future decisions. It does not help a county decide on a first project before any such reports exist, which is exactly Otoe’s situation.

    What Developers Can Take From Otoe

    Cannon’s advice to developers was practical: tell residents early. He described what happens when neighbors learn about a project from each other, through someone who “just signed this big contract for a right of way.” In Otoe and Gage, residents appear to have learned of the potential project through press reporting on a private utility meeting and through land options. It was not an announcement from the companies. A community that pieces a project together from secondhand reports tends to fill the gaps with worst-case assumptions.

    The lesson for anyone siting AI capacity in rural areas is that the time-consuming work may be local rather than technical. That means disclosing water and cooling plans, explaining who pays for power, and engaging before the zoning agenda is set. Developers who bring those answers to a county writing its first ordinance have a chance to help set the terms. Developers who arrive afterward will be working within rules written without their input.

    Background

    Otoe County sits in southeast Nebraska. Its county seat is Nebraska City, south of Omaha and east of Lincoln. Like many rural counties, it has previously dealt with controversial large developments such as wind and solar farms. Its land-use rules were not written with hyperscale data centers in mind. Hyperscale refers to the very large facilities built by major cloud and AI companies.

    Demand for AI computing has driven a nationwide search for sites with available land, power and water. Established hubs such as Northern Virginia have run into grid limits. Nebraska responded in 2026 with a law allowing dedicated private power generation for large customers and a separate law requiring annual public reporting on data center energy and water use.

    Sources

    Source: A Nebraska county just banned new data centers for up to a year. More could follow, Nebraska Public Media (Flatwater Free Press), on Otoe County’s permit suspension and the spread of data center moratoriums across Nebraska.

  • Maine Governor Vetoes First Statewide Data Center Moratorium: A Template Emerges

    Maine Governor Vetoes First Statewide Data Center Moratorium: A Template Emerges

    Maine Governor Janet Mills has vetoed legislation described as a landmark data center ban, according to an April 25, 2026 report from the Maine Morning Star. The bill would have made Maine the first U.S. state to impose a statewide moratorium on new data center development — a sharp escalation of a siting fight that has, until now, played out mostly at the town and county level.

    The veto keeps Maine formally open to data center projects and hands the industry a notable, if narrow, victory in the first statewide test of the moratorium movement.

    Executive Summary

    The significance of this veto extends well beyond Maine, a state that has never been a major data center market. Legislatures across the country have been debating how to respond to the wave of AI-driven data center construction — its electricity demand, its water use, its tax treatment, and its effect on ratepayers. Maine’s bill was the movement’s most aggressive expression: not stricter permitting or ratepayer protections, but a statewide halt. Mills’ veto establishes the first precedent for how a governor responds when that idea actually reaches a desk.

    For the industry, the takeaway is double-edged. A moratorium passed a state legislature — proof the backlash has matured from zoning-board resistance into statewide lawmaking. But it also failed at the executive branch, suggesting that even in states with little economic stake in the sector, governors are reluctant to slam the door entirely. How durable that reluctance proves — and whether Maine’s legislature attempts an override — will shape the template other states copy.

    From Zoning Boards to Statehouses

    Data center opposition is not new, but its venue is changing. For years, siting fights were hyper-local: individual towns and counties passing zoning restrictions or temporary building pauses while they studied noise, land use, and utility impacts. A statewide moratorium — a legislated pause on an entire category of development across a state’s whole territory — is a categorically different instrument, and Maine’s bill appears to be the first of its kind to clear a legislature.

    That escalation matters because state-level action changes the risk calculus for developers. A hostile town can be routed around; a hostile state cannot. Site selectors already screen states on power availability, tax incentives, and permitting speed. If moratorium bills become a live possibility, legislative risk joins that screening list — and states seen as wobbly may be quietly dropped from shortlists long before any bill passes.

    Why a Governor Blinked at a Ban

    The reported veto is consistent with a pattern visible across state politics: even leaders sympathetic to concerns about energy demand and ratepayer costs tend to resist outright prohibitions on investment. A moratorium forecloses future tax base, construction employment, and the option value of attracting projects on the state’s own terms. For a governor, signing the nation’s first statewide ban also carries signaling risk — branding the state as closed to a technology sector into which capital is flowing at historic rates.

    The source report does not include Mills’ stated rationale, so the specific reasoning here is unconfirmed. But the structural logic is worth noting: vetoing a moratorium is not the same as endorsing unregulated growth. Governors in several states have paired resistance to bans with support for targeted measures — cost-allocation rules that shield residential ratepayers, or minimum efficiency standards. Whether Maine pursues that middle path is one of the most important open questions the veto leaves behind.

    Maine as an Unlikely Bellwether

    Maine is a curious venue for the first statewide test. It is a small New England market with high electricity prices, a constrained regional grid, and no significant hyperscale footprint — precisely the profile of a state with little to lose from a moratorium and, arguably, little to attract without one. That is what makes the veto instructive: if a ban could not survive the executive branch in a state with minimal industry presence, its odds look longer in states where data centers already anchor local tax bases.

    The counter-reading deserves equal weight. The bill’s passage shows that in states where the industry has no built-in constituency — no employees, no host-community payments, no utility revenue on the table — a moratorium can command a legislative majority. As AI-driven load growth pushes developers into new geographies beyond Virginia, Texas, and Arizona, they will increasingly encounter exactly these constituency-free states. Maine may be less an outlier than an early sample of the terrain ahead.

    The Template for the Fights to Come

    Both sides of the siting debate will study this sequence. For moratorium advocates, the lesson is that legislative passage is achievable but insufficient; veto-proof margins or governors’ races become the real battleground. For the industry, the lesson is that goodwill cannot be assumed — the case for data centers now has to be made state by state, with concrete commitments on grid costs, water, and local benefit, rather than relying on the sector’s momentum.

    The practical winners in the near term are developers with optionality: those able to shift projects toward states offering regulatory certainty. The losers are harder to name from this report alone — it is not clear any specific Maine project was pending. The broader risk is a patchwork: a national map where the rules for building digital infrastructure diverge sharply by state, complicating the long-term planning that grid operators and hyperscalers both depend on.

    Background

    Data center siting has become one of the most contested land-use questions in the U.S. as AI workloads drive a historic construction boom, with projects measured in hundreds of megawatts of electricity demand. Opposition that began at zoning boards — over noise, water, and land — has increasingly moved into state legislatures, which have debated tax-incentive rollbacks, ratepayer protections, and disclosure requirements.

    Maine had largely sat outside this boom: a small, energy-constrained New England state without a meaningful data center footprint. Its legislature nonetheless produced what was reported as the nation’s first statewide moratorium bill, and Governor Janet Mills — the state’s Democratic governor since 2019 — vetoed it in April 2026, creating the first executive-branch precedent in the statewide moratorium debate.

    Source: Gov. Mills vetoes landmark data center ban — Maine Morning Star report, April 25, 2026, on the veto of what was described as the first statewide data center moratorium bill in the U.S.