Will Monarch's Data Center Find Its Operator Soon?

The site exists. The ambition is clear. But without a confirmed operator, Monarch's data center project sits in a familiar kind of limbo — one that's become increasingly common as industrial land development races ahead of the demand signals needed to actually build.

That gap between "we have land" and "we have a tenant" isn't a failure. It's a structural feature of how large-scale infrastructure gets done. But it does create a specific planning problem: you can't size your utility infrastructure until you know who's moving in, and you can't attract the right operator until you can show them the infrastructure exists.

This is the core tension at the heart of Monarch's development, and it's worth understanding in detail — because how this project resolves it will tell you a lot about where data center development is headed.

Understanding Monarch's Data Center Context

Monarch's project is being positioned within a broader industrial development framework. That framing matters. Data centers don't exist in isolation — they anchor ecosystems. A confirmed hyperscale operator brings not just power draw and fiber demand, but secondary development: cooling equipment suppliers, security contractors, network interconnection facilities, and, in some cases, on-site generation assets.

The operator isn't just a tenant — they're the load profile, the utility agreement, the construction specification, and the financing thesis all rolled into one.

Without that operator confirmed, Monarch's utility needs remain genuinely unknown. This isn't a communications gap or a PR strategy. It's a technical reality. A 50MW colocation facility has fundamentally different electrical infrastructure requirements than a 200MW hyperscale campus. The transformer sizing, substation interconnection voltage, cooling water volumes, and backup generation capacity — all of it flows from the operator's workload architecture, which flows from their customers' requirements.

This is why developer-led data center projects that break ground without an anchor tenant carry real risk. Land is the easy part. Utility infrastructure, particularly at the voltage levels data centers require, takes years to permit and build.

The Role of Utility Needs in Data Center Functionality

Data centers are, at their core, power conversion machines. They take electricity, run it through servers, and exhaust heat. Everything else — the fiber, the water, the redundancy systems — exists to support that fundamental transaction.

A mid-sized data center might draw 50–100MW continuously. A large hyperscale facility can exceed 500MW. For context, 100MW is enough electricity to power roughly 80,000 average American homes. When a utility has to accommodate that kind of load from a single customer on a single site, the planning implications are significant: transmission upgrades, substation builds, interconnection queue positions, and potentially new generation capacity if the regional grid is already stressed.

Utility planning for a data center isn't an operational detail — it's a multi-year infrastructure project in its own right.

What makes this particularly complex for Monarch's situation is that different operators have materially different requirements beyond raw power. Some require 2N redundancy on power feeds, meaning every critical system has two fully independent backups. Others operate at lower redundancy tiers but demand ultra-low latency fiber interconnections. Cooling requirements vary by server architecture — air-cooled, liquid-cooled, and immersion-cooled deployments all have different water and HVAC footprints. The utility provider and the site developer need to know which scenario they're planning for, and right now, they don't.

Challenges in Securing Data Center Operators

The data center market is not short on demand. Global data consumption is climbing, AI workloads are pushing power density to new extremes, and every major cloud provider is in a multi-year capital expenditure cycle measured in the tens of billions. So why do projects like Monarch's struggle to confirm operators quickly?

The short answer: operators have options, and they know it.

Hyperscalers — Amazon Web Services, Microsoft Azure, Google Cloud, and Meta — are sophisticated real estate players. They run formal site selection processes that evaluate dozens of criteria simultaneously: grid reliability and available capacity, transmission costs, renewable energy access, water availability for cooling, permitting timelines, tax incentives, labor markets, and latency to population centers. A site that checks nine out of ten boxes loses to the site that checks all ten.

The competition isn't just among developers pitching operators — it's among states, utilities, and entire regional grids competing for the same pool of capital.

Emerging markets like the Mountain West, the Midwest, and parts of the Southeast have been aggressively pursuing data center investment by pairing available land with utility rate incentives and renewable energy portfolios. Monarch's project has to compete in that environment. The presence of a broader industrial development context can help — operators prefer sites where supporting infrastructure already exists — but it's not a substitute for a compelling utility story.

There's also the timeline problem. Hyperscalers are operating on 18–36 month build cycles. If the utility interconnection for Monarch's site requires a 24-month transmission upgrade, that's potentially a disqualifying constraint for an operator who needed to be online yesterday.

Future Trends in Data Center Utility Planning

The way data centers are planned and powered is changing fast, and that evolution is relevant to how Monarch's project should position itself.

Power density per rack has roughly tripled over the last five years, driven almost entirely by AI inference and training hardware. Nvidia's current GPU clusters can push 100kW per rack — a number that was considered extreme for an entire row of servers just a decade ago. That density shift is breaking conventional data center cooling and power distribution architectures. Operators increasingly want sites that can accommodate liquid cooling infrastructure from day one, not as a retrofit.

On the utility side, sustainability requirements are no longer optional for tier-one operators. Microsoft, Google, and Amazon have all made public commitments to carbon-free energy, and they increasingly structure their site selection and power purchase agreements around that commitment. A site with clear access to renewable generation — whether through direct interconnection to wind or solar, or through a utility with a strong clean energy portfolio — has a structural advantage in operator negotiations.

The developers who win in this environment aren't just selling land — they're selling a credible path to clean, reliable, abundant power.

Battery storage integration is another emerging factor. As grid interconnection queues lengthen and renewable generation grows more variable, data centers are increasingly being designed with on-site battery storage to manage peak demand, provide grid services, and reduce exposure to time-of-use pricing. A site that can accommodate a co-located battery storage system is more attractive than one that can't.

Next Steps for Monarch's Development

Monarch's path forward runs through two parallel workstreams that have to develop simultaneously, even though each depends on the other.

First, the utility relationship needs to advance far enough to produce a credible range of infrastructure scenarios. That means working with the relevant utility to understand what load sizes are achievable on what timelines, at what cost, and with what renewable energy composition. That analysis doesn't require a named operator — it requires a set of planning scenarios. Done well, it becomes a powerful tool in operator recruitment because it replaces speculation with specifics.

Second, the operator recruitment process needs to accelerate with a targeted, criteria-specific pitch that matches Monarch's actual advantages to the actual requirements of the most likely tenant profiles. Not every site is right for every operator. A 100MW colocation play looks different from a hyperscale greenfield play. Knowing which category Monarch's site fits — and pursuing that tier aggressively — is more productive than broadcasting to everyone.

The sites that move from "announced" to "operational" fastest are the ones where the developer and the utility have done the hard planning work before the operator arrives, not after.

Stakeholders watching this project — infrastructure investors, regional utilities, industrial park developers, and neighboring municipalities — all have skin in the game. Clarity on the operator and utility path is ultimately good for everyone in that ecosystem. The longer the uncertainty persists, the more the adjacent development opportunities get put on hold.

Monarch's data center isn't just a real estate transaction. It's a test case for how infrastructure development at this scale gets sequenced. Get the utility planning right, and the operator follows. Get the operator first and leave utility planning to chance, and you risk the kind of costly retrofits and interconnection delays that have derailed more than a few high-profile projects.

The sequencing matters as much as the ambition.

[INTERNAL LINK: data center development trends]

[INTERNAL LINK: utility infrastructure planning]

[INTERNAL LINK: securing data center operators]

Ready to explore the InfraSale Marketplace? Join us now!