Cleveland Rejects $1.6B Data Center: What's Next?
Cleveland's rejection of a $1.6B data center plan raises questions for investors and the future of local infrastructure. What’s next?
A $1.6 billion project. A 150MW hyperscale campus. Three buildings across 35 acres in a neighborhood that could use the economic activity. Cleveland's answer? No.
Mayor Justin M. Bibb announced on May 14 that the city had rejected the permit for private credit firm Lakeland Equity Group's proposed data center at 3560 E 55th St in Slavic Village — a southeastern Cleveland neighborhood currently housing trucking company Morabito Enterprises. The rejection was swift enough that Lakeland publicly called it "abrupt." That word choice matters. It suggests a process that didn't end the way Lakeland expected and likely signals that the door isn't entirely closed.
What happened here, why it matters beyond Cleveland's city limits, and what it signals for developers navigating an increasingly complicated infrastructure approval environment — that's what's worth unpacking.
The Proposal, By the Numbers
Lakeland positioned this as Cleveland's first hyperscale facility. The pitch was straightforward: 300,000 square feet of purpose-built data center space across three buildings, powered by 150MW of IT capacity, and equipped with what the company described as "advanced power, cooling, and fiber connectivity." The identity of the anchor tenant was never disclosed publicly — a common practice during the early permitting phase, though it does limit the city's ability to weigh the actual demand behind the proposal.
150MW is not a small project. For context, a single hyperscale campus at that capacity can support millions of cloud workloads simultaneously, and projects of this scale typically attract anchor tenants from the hyperscaler tier — think Microsoft, Amazon Web Services, or Google. Whether Lakeland had a committed end user or was speculating on future demand is a detail the public record doesn't resolve, but it's exactly the kind of question city officials and community stakeholders ask.
At $1.6 billion in total investment, that's roughly $10.7 million per MW — in the range of what modern hyperscale builds cost when you factor in land, infrastructure upgrades, and construction. Lakeland describes itself as specializing in projects with funding equity shortfalls in the $1-10 million range, which raises a reasonable question about how a firm of that stated scale was positioned to lead a $1.6 billion development. Public information about Lakeland Equity Group is sparse, by the source reporting's own admission.
Why Cleveland Said No
The city has not released a detailed public explanation for the rejection beyond Mayor Bibb's announcement. That absence of specifics is itself revealing — rejections with clean technical justifications tend to come with documentation. When they don't, the reasons are usually more complex: community opposition, concerns about neighborhood fit, questions about the developer's track record, or political calculus.
Slavic Village is a neighborhood with a history. It bore some of the worst damage of the 2008 foreclosure crisis and has been the subject of revitalization efforts for over a decade. A 35-acre industrial conversion in that context carries weight beyond zoning. Residents there have seen promises before. A data center, by its nature, doesn't deliver the kind of dense employment that transforms a neighborhood — a 150MW facility might employ a few hundred people during construction and a fraction of that permanently.
That's the tension at the core of most data center siting disputes right now: the investment numbers look transformative, but the ongoing job creation often doesn't match the scale of infrastructure being built or the disruptions to existing communities. Lakeland's statement emphasized "job-creating project" in its response, but it offered no specifics on how many jobs, what type, or what the timeline would look like.
Without the city's formal rejection rationale on the record, investors and developers are left reading between the lines. That uncertainty is uncomfortable — and instructive.
What This Means for Infrastructure Investors
Cleveland's rejection doesn't exist in a vacuum. Across the country, data center developers are running into the same friction: strong macro demand for compute infrastructure colliding with local resistance, infrastructure constraints, and municipalities that are increasingly aware of their leverage in these negotiations.
The approved projects are clustering in places that have made deliberate choices to attract them. Columbus, not Cleveland, is Ohio's data center hub — a pattern the source reporting notes directly. Columbus has the power infrastructure, the fiber density, and an established approval track record that makes it a lower-risk environment for large-scale builds. When a city like Cleveland enters this conversation late and rejects a major proposal early, it doesn't just lose one project. It signals to the broader developer market that the approval environment is unpredictable.
For investors evaluating infrastructure development opportunities, permitting risk is now as material as power availability or land cost. A rejection like this one — described as "abrupt" by the developer — is exactly the kind of outcome that adds a risk premium to any future Cleveland proposal.
There's also the question of what Lakeland does next. The company said it was "considering options for immediate next steps" and expressed a desire to continue working with local officials and community members. That language reads as an appeal process in the making, not a clean exit. If Lakeland pursues a legal challenge or resubmits with modifications, this story has more chapters.
The Community Calculus
The community dimension here is genuinely complicated, and it deserves more than a line about "mixed reactions." Slavic Village residents aren't monolithic. Some would welcome any large-scale investment that signals confidence in the neighborhood. Others have watched previous development promises fail to deliver lasting benefits to existing residents — rising land values, displacement pressure, and jobs that don't match the skill profile of the local workforce are all legitimate concerns.
A hyperscale data center brings construction jobs, municipal tax revenue, and potentially significant utility infrastructure upgrades that benefit the broader area. Those are real. What it doesn't bring is retail foot traffic, neighborhood activation, or the kind of mixed-use development that changes how a place feels day to day. A 300,000-square-foot data center is, by design, a fortress — not a community anchor.
That distinction matters when a city is deciding what it wants a 35-acre site to become.
Where Cleveland Goes From Here
Cleveland isn't closed to data center development by any means. But this rejection raises the bar for what a proposal needs to look like to succeed. Future developers targeting Cleveland will need to come with a disclosed end user, a credible community engagement process that starts before the permit application, and a workforce development commitment that's specific enough to actually mean something.
The site at 3560 E 55th St will return to the conversation in some form — either through Lakeland's anticipated next steps or through a different developer taking a run at the location. Morabito Enterprises, the current occupant, isn't mentioned as a willing seller, which adds another layer of complexity.
Longer term, the pressure on secondary markets like Cleveland isn't going away. Power-constrained primary markets and rising land costs in established data center corridors are pushing developers to look at cities that haven't historically been in the conversation. Cleveland has the Great Lakes as a cooling resource, access to regional fiber routes, and significant available industrial land. The infrastructure fundamentals aren't bad. What's missing is a clear municipal framework for how data center development fits into Cleveland's broader economic development priorities — and until that exists, developers are navigating in the dark.
The next proposal to land on Mayor Bibb's desk will need to answer that question before it gets to permitting.
Ready to explore opportunities in the infrastructure space? Visit our marketplace for more insights and options! [INTERNAL LINK: infrastructure opportunities]