Michigan law gives the university broad control over its land, but utility service, environmental permits, and political challenges remain unresolved.
On August 11, the University of Michigan named a 144-acre parcel on Textile Road, along the Huron River in Ypsilanti Township, as the preferred site for the $1.25 billion research supercomputing center it is developing with Los Alamos National Laboratory. Township officials learned it was coming by text message, moments before it went out.
Supervisor Brenda Stumbo vowed to fight the decision "to the end." The more surprising dissent came from inside the university: Regent Paul Brown publicly opposed his own institution's choice the day it was announced. Behind the statements: a year of township board resolutions, at least three letters from Rep. Debbie Dingell, a petition from roughly 900 U-M employees, faculty and students, and a 12-month water-and-sewer moratorium at the regional utility.
The project is planned to start around 50 megawatts and reach a 100 MW ceiling. U-M calls that "less than 1/10th the energy of commercial data centers," a comparison the university offers without naming a denominator. (Planet Detroit reported a projected 110 MW ceiling in March; the FAQ now says 100.)
The dispute's structure is what carries beyond Michigan. Local zoning review does not reach the university, so the township's opposition runs through the levers that remain: water, environmental permits, the legislature, Congress. The past year is a running test of what those levers can move.
Michigan's 1963 constitution vests U-M's governance in an elected Board of Regents with "general supervision of its institution and the control and direction of all expenditures from the institution's funds"; Michigan State and Wayne State have equivalent boards. The text says nothing about zoning. In Booth Newspapers v. Regents (1993), Michigan's Supreme Court called the university "an independent branch of the government of the State of Michigan," supreme within the confines of its operations and the allocation of its funds, while cautioning that it "is not an island." The settled reading across coverage of this dispute is that local zoning does not bind the university on land it owns. "The Constitution is silent on the issue of local governments and universities and how they should operate in the same sandbox," Citizens Research Council of Michigan president Eric Lupher told The Detroit News. Stumbo has conceded the practical consequence: once U-M bought the land, the township "had no power to intervene."
One qualification cuts against the cleanest version of that story. U-M notes the parcel was already zoned light industrial, and the township approved an Amazon last-mile distribution facility on it in 2021, a project the university says would have brought a larger footprint and more traffic than the computing center. That does not dissolve the autonomy question; the township never got to weigh this particular use. It does complicate the assumption that a zoning vote, had one existed, would have blocked the project.
Fifteen miles away is the control case. Saline Township's board and planning commission rejected the Related Digital campus serving OpenAI and Oracle's Stargate buildout in September 2025, a project with roughly $16 billion in reported financing and 1.4 gigawatts of contracted DTE Energy supply. The developer sued; a settlement let construction begin within weeks. Saline lost, but it lost holding a zoning vote the developer had to sue its way past.
Ypsilanti Township never had one.
The backdrop is statewide: at least 19 Michigan municipalities have adopted data-center moratoriums in Stargate's wake, and Gov. Gretchen Whitmer's July 15 growth plan asks developers to sign a voluntary responsibility pledge; six companies did within 24 hours. U-M says it will follow the pledge's principles. Doug Winters, the township's attorney, on what that is worth: "It's not enforceable… Boy Scouts and Girl Scouts give a pledge."
The project is two buildings on one site: a 240,000-square-foot federal research facility supporting LANL's national-security mission, "including classified research," and a roughly 50,000-square-foot academic center for unclassified, publishable work, all per U-M's project FAQ, whose figures are the university's own representations rather than audited numbers. The $1.25 billion: $300 million from LANL, $220 million from U-M, $630 million in university-facilitated financing, and a $100 million state site-readiness grant. U-M describes it as LANL's first permanent research presence in Michigan.
The passage that matters most to the supercomputing field concerns capacity, and it supports less than it might seem to. In a July 10 letter answering 21 questions from Dingell, U-M President Domenico Grasso and LANL Director Thom Mason wrote that the laboratory "is currently expanding its computing facilities in Los Alamos to support next generation computers for these missions and is exploring options for future computing facilities as computational workload demands increase." The next-generation systems at Los Alamos are Mission and Vision, the Vera Rubin machines NNSA presented under the Genesis Mission in July; Mission is the ATS-5 procurement replacing Crossroads for stockpile-stewardship simulation. The public documents do not say whether the Michigan center addresses a physical constraint at Los Alamos, or whether it will host systems related to Mission and Vision at all. What the letter establishes is narrower: workloads are growing, and future facilities are being explored.
On the work itself, the letter is careful. It lists what will not be on site (no nuclear materials, no plutonium pits, no manufacturing, no real-time defense operations) and offers that "it would be reasonable to assume computing facilities supported by the laboratory budgets are contributing to nuclear security." Michigan Public has reported that "officials have confirmed" the laboratory's share of the computing power will support production of plutonium pits, the fissile cores of nuclear weapons, carried out elsewhere. That characterization is the station's; the documents U-M and LANL have signed stop at "reasonable to assume."
Much about the computing itself is not public. The sources reviewed for this article do not identify a vendor, an architecture, or who would operate the classified building, whether LANL, its managing contractor, or another entity, nor the funding source behind LANL's $300 million contribution. "Federal" in U-M's materials describes the building's research mission; ownership and operating arrangements have not been spelled out. Twenty months after the announcement, the hardware is the quietest part of the project.
Laid end to end, the chronology is compact. October 2024: the Regents approve the first Textile Road parcel, about 20 acres. December 2024: U-M and LANL announce the project. June 2025: the Regents authorize 124 additional acres. August 2025: the township board urges U-M to build at the Willow Run-adjacent American Center for Mobility site instead; U-M reviews that site twice, once at township request, and drops it over brownfield-redevelopment requirements and what it calls an unachievable "level of local governmental partnership and support." March 2026: the purchase closes, and the township supervisor learns of it by text message. March 31: the board resolves "strong and unequivocal opposition" to a LANL facility anywhere in the township. April 15: the board requests a utility moratorium. April 22: the Ypsilanti Community Utilities Authority adopts one for 12 months, with no will-serve letters and no capacity reservations, covering data centers and, explicitly, "high-performance computational centers." July 10: the Grasso-Mason letter tells Dingell that "no final site has been selected," and discloses the cooling review. August 11: Textile Road is the preferred site, 32 days after the no-final-site letter.
U-M's account of the acreage, from the same letter: "The project itself has not expanded. The additional acreage was acquired to provide flexibility for locating the electrical infrastructure." The township reads the same dates as a project assembled quietly and disclosed late; "because of this lack of transparency, Ypsilanti Township does not want you as a neighbor," Dingell wrote in June. Both readings rest on the same documents.
The employment numbers hold a definitional gap. U-M's December 2024 announcement promised at least 200 high-paying jobs; the current FAQ separates the prediction into roughly 300 union construction jobs, more than 200 "permanent research positions," and 30 to 50 on-site technical support roles; township materials say the promise was "revised" to approximately 35. The FAQ does not state where the research positions would be based. Neither "200 on site" nor "35 total" is established by the documents.
The most consequential lever so far is water, and its effect should be stated precisely. U-M's original design used evaporative cooling; an earlier version of the project FAQ put demand around 500,000 gallons a day against 8 to 10 million gallons of stated excess supply, figures reported at the time by Planet Detroit and since removed from the FAQ. After YCUA adopted its moratorium on April 22, U-M and LANL told Dingell on July 10 that they were "pivoting to and actively exploring" a closed-loop cooling system in place of the evaporative design, one that "would drastically reduce or eliminate daily water consumption for cooling," with reclaimed wastewater also under evaluation. U-M attributes the review to community feedback. The public record does not establish that the moratorium caused the change, and the design remains under evaluation, costs and environmental impacts included.
The cooling discussion mixes three distinct things, worth separating. Direct-to-chip, which U-M has confirmed, describes how heat leaves the silicon; it is the direction large-scale computing is heading generally, and NVIDIA is standardizing warm-water versions of it for its own platforms, though nothing ties this facility to that spec. Whether the facility-level loop is closed, what temperature it runs at, how the building finally rejects heat, and who supplies the system are all undisclosed. Water capacity is the third thread: the letter says any municipal purchase would come through YCUA, which draws on the Detroit River system rather than local sources, and U-M has put its projected draw at under 10 percent of excess capacity, while YCUA has separately reported 4 to 5 million gallons a day of excess wastewater-treatment capacity, a different constraint from drinking-water supply. U-M says the Huron River will be neither source nor discharge.
The rest of the inventory moves slower. U-M concedes it needs stormwater and wetlands permits from EGLE, Michigan's environmental agency. Winters says the township will invoke the Michigan Environmental Protection Act to defend the river corridor; no suit has been filed. In Lansing, a three-lawmaker package, House Joint Resolution X and House Bills 6120 and 6121, would subject university land acquired after 2027 to local zoning, leaving this project untouched. Rep. Jimmie Wilson Jr. of Ypsilanti has separately proposed rescinding the $100 million grant, and any constitutional amendment needs two-thirds of both chambers plus a statewide referendum. Only the moratorium runs on the project's clock: it expires in April 2027, and U-M's December 2024 schedule had construction beginning in 2026.
Brown's dissent moved the critique inside the boardroom. The site "is in its natural state, is on the Huron River, and... is opposed by the local residents," the Regent said, and the university "has failed to engage in an adequate conversation with those most affected." He said the siting "looks like environmental racism"; Winters calls it "a textbook example" of the same. The statistics invoked around that charge are screening indicators, not proof of intent: per-capita income of $36,162 in the township against $52,714 countywide, per Census figures, and census tracts near the adjacent West Willow neighborhood in the 85th-to-88th percentile on MiEJScreen, the state's comparative environmental-justice screening tool. The record reviewed for this article contains no direct U-M answer to the characterization; the university's broader response points to three public events in a year, a riverfront it says will stay undeveloped, a substation it funds itself, and "partnership opportunities" it says the township has not taken up.
The fiscal asymmetry is documented more simply. As "a state university and a state instrumentality," U-M pays no property taxes on the land, and the July letter describes no payment-in-lieu arrangement, only that unanswered partnership offer. Dingell's summary: the township "would see little benefit from an institution that pays no property taxes."
The structural picture, on the numbers: the US commercial buildout is projected in the 100-gigawatt range; this facility's ceiling is 100 megawatts, one-tenth of one percent of that. The moratorium's text draws no such distinction, placing "high-performance computational centers" in the same restricted category as hyperscale data centers. On the record assembled here, the reception a large computing facility receives has not depended on whose workloads it runs. National labs have started engaging the buildout from the other side (ORNL runs an institute on next-generation data centers); in Michigan, a laboratory is a principal in a siting dispute.
What happens next has dates. U-M hosts a community town hall on September 9, its third public event in a year by its own count. The YCUA moratorium runs to April 2027. The December 2024 plan called for construction to begin in 2026 and full operation in 2030; the August announcement, which named only a "preferred" site, attached no updated schedule. The public sources reviewed for this article still do not say what machines the buildings will hold.
The SCN Staff is a small AI editorial squad working under human direction. Each agent owns one job.
Scout does the research. It runs down primary sources and checks what's already been published, on SCN and everywhere else, before a story gets written. If a claim can't be traced back to a real document, Scout flags it.
Forge writes. It takes what Scout found and turns it into a draft, argument and sentences and all. Every SCN piece starts here, then gets sharpened.
Cipher handles search: the titles, descriptions, and keyphrase work that decides whether a good article ever gets found. Least glamorous job on the squad. Also one that matters more than it looks.
Pixel makes the visuals. Images, charts, the occasional diagram, all built to SCN's brand instead of pulled from a stock library. When something's easier to see than to read, it goes to Pixel.
Editorial judgment and the final call stay with the humans. So does the fact-checking.
