Brighton's 2.52 Million-Square-Foot Data Center Plan Is Withdrawn. What Happens Next?

October 26 update: Brighton adopted the one-year moratorium 9-0 on October 20. Read the adoption update and regional development analysis. The earlier first-reading account follows.

The rezoning application behind Brighton's proposed 2.52 million-square-foot data center campus has been withdrawn. For residents near County Road 4 and 50th Avenue, that removes the application that brought the prospect of eight large computing buildings into their neighborhood. For landowners and developers, it changes the near-term outlook for data center development inside Brighton.

City officials announced the withdrawal at the October 6 council meeting, according to Colorado Public Radio's coverage. The council also advanced a one-year pause on data center applications. Brighton's official October 7 announcement says the ordinance requires a second reading, scheduled for October 20, before adoption.

As of October 13, the accurate description is a withdrawn rezoning application and a moratorium awaiting its second vote. The site's longer-term future remains unresolved.

What was proposed near Lochbuie?

The concept called for eight two-story buildings of approximately 315,000 square feet each near Brighton's border with Lochbuie. Residents obtained the early planning records through an open-records request. Denver7's original reporting described pre-application discussions between planning firm Dewberry and city officials in January and July 2025.

Those dimensions help explain the public response. Eight buildings, their cooling equipment, electrical facilities, access roads and backup power systems would create a substantial industrial presence. Residents were evaluating how that presence would fit beside the places where they already lived.

Our earlier analysis of the Brighton campus proposal examined the location and its infrastructure context. The withdrawal changes the project's application status. The documents preserve the withdrawn concept and the issues that prompted the debate.

Square footage also leaves major operating questions unanswered. Any renewed proposal should publish its requested electrical load, cooling design, water budget and equipment layout. Those details would allow residents and reviewers to assess the actual facility, including its first phase and potential expansion.

Why the withdrawal matters

The application provided a specific route for changing the site's zoning. Its withdrawal means that route is no longer advancing through the submitted application. A claim that the campus is still moving toward approval on the same schedule would need new evidence.

The withdrawal also leaves questions that the public record reviewed for this article does not settle. Will the landowner pursue a different use? Could a smaller data center return? Would another developer take an interest after Brighton establishes its rules? Those possibilities require new filings or statements from the parties involved.

For now, residents can follow a much clearer next step: the city's rulemaking. Brighton has an opportunity to decide where this use belongs, what an applicant must disclose and which operating commitments the city can enforce.

That work deserves public attention even with the application withdrawn. Rules written during a pause can determine the shape of future proposals long after the original controversy fades.

What the proposed moratorium would cover

Brighton's announcement describes a pause covering the acceptance, processing and approval of permits, licenses, zoning and other land-use requests involving data centers. The city identifies water, wastewater and electrical power among the infrastructure issues it wants to examine. It also describes a possible additional 90 days if regulatory work remains unfinished when the year ends.

The practical implication for a prospective developer is substantial. A purchase model that assumes a quick application needs to be revisited. Holding costs, utility-study timing and the availability of alternative sites all deserve another look.

A landowner may still want to understand a property's long-term potential during that period. The useful work would be to establish its physical constraints, utility relationships and likely compatibility with emerging standards. Any proposed transaction should account for the uncertainty around when applications could proceed and what the eventual rules would require.

Brighton should use the time to answer specific questions

A productive rulemaking process should leave residents and applicants with requirements they can understand before a hearing begins.

Start with location. The city should identify appropriate districts and evaluate the relationship between industrial sites and nearby housing. Setbacks should be considered alongside the placement of fans, generators, substations and access roads. A large parcel can still produce a poor layout if its equipment is concentrated near homes.

Water reporting should show commissioning demand, annual operating demand and peak-day demand. Each estimate should identify the phase of development it covers. Residents should be able to see what changes during hot weather, maintenance or expansion.

Noise rules should explain where sound is measured, which operating conditions must be evaluated and how complaints will be investigated. Normal operations and generator testing deserve explicit treatment. A permit is more useful when its promises can be checked after the buildings open.

The city should also require a clear explanation of infrastructure responsibility. Who supplies power? Which upgrades are needed? Who pays for them? What evidence supports the delivery schedule? These questions belong in the public explanation of a large project.

Our position is straightforward: Brighton should use the pause to produce a usable approval process with enforceable standards. Residents deserve predictable protections. Applicants deserve to know what a complete and acceptable proposal must demonstrate.

Crusoe's Spark Factory is a separate Brighton development

Brighton already has another connection to AI infrastructure. In March, the city announced Crusoe's planned Spark Factory at 22600 East I-76 Frontage Road. The city's announcement described a 352,000-square-foot manufacturing facility, approximately $200 million in investment and more than 200 expected jobs.

That facility is intended to manufacture modular data center units. It is a separate development from the eight-building campus near County Road 4. The announcement does not establish a connection between Crusoe and the withdrawn proposal.

Keeping the two projects distinct helps explain Brighton's choices. Manufacturing computing infrastructure and operating a large computing campus create different development questions. Each project needs to be assessed against its own site, equipment, demands and approvals.

What this means for the I-76 corridor

Brighton's decision should change how developers evaluate sites within the city. It should also prompt a more careful look at jurisdiction boundaries throughout the northeast Front Range.

Properties marketed with the same general location can fall under different land-use authorities and utility providers. The controlling jurisdiction needs to be confirmed for the actual parcel. A nearby approval, factory or transmission line offers context, while the candidate site still needs its own evidence.

LandmAIn's Colorado infrastructure map helps organize that initial comparison. Our developer guide to Colorado's changing data center market explains how to connect the location screen to permitting, utility and community questions before committing to a site.

The next decision is October 20

Brighton's scheduled second reading is the immediate event to follow. Residents can check the city's agenda center for the posted materials and meeting information.

After that vote, the quality of the rulemaking will matter more than the length of the pause alone. Look for draft definitions, proposed districts, operating standards and opportunities to comment. Those documents will provide the first concrete indication of what a future Brighton data center would have to deliver.

For the withdrawn campus, the next meaningful signal would be a new application or an announced change in plans. Until then, Brighton belongs on a policy watch list, with its near-term data center development assumptions revised accordingly.