Last Update: 09/17/2026 at 10:34 PM EST

Morning Briefing: Data Centers

Tuesday, August 18, 2026

August 18, 2026

Ohio Financing Advances as Project Gates Multiply

Yesterday's most consequential development came in Ohio, where reported Nvidia-backed financing gave OpenAI's proposed Pike County campus a more defined route from an extraordinary capacity target to an operating structure. But the same day's disputes in Nashville and Wisconsin reinforced a counterweight: large data-center projects are only as executable as their power commitments, financial safeguards, and durable permits.

This is not evidence of a single national regulatory turn. It is a growing set of project-specific gates—some financial, some grid-related, some political—alongside continued willingness to assemble unusually large pools of capital for AI infrastructure.

CNBC and AOL reported that Nvidia, OpenAI, SB Energy, and SoftBank have advanced a financing and leasing framework for the planned Ohio campus. SB Energy would build, own, and operate the site under a 20-year lease; Nvidia is reported to be investing $1.5 billion in SB Energy and providing up to $105 billion in lease-payment support. The plan calls for 4.25 GW of computing capacity to begin arriving in phases in 2028, with a possible expansion to 8 GW, backed by 10 GW of generation and at least $4.2 billion in regional grid investment. The reported terms remain subject to execution and have varied across accounts, but the arrangement is materially more concrete than a conventional expansion announcement.

The significance is not simply the scale of the guarantee. It is the division of responsibilities: the tenant, chip supplier, developer, generation sponsors, and grid operator all need aligned commitments before such a campus can move. The Ohio project therefore offers a visible example of how hyperscale AI buildouts are being financed as integrated power-and-compute systems rather than as standalone real-estate developments.

In Nashville, DC BLOX took its dispute with Metro into federal court over measures intended to stop a planned two-facility project near the Nashville Zoo. The company says it had secured permits before the city imposed new restrictions and alleges violations of vested rights and constitutional protections. Metro says its actions were lawful. No ruling has been issued, but the conflict now turns on whether earlier approvals can withstand later land-use restrictions and eminent-domain efforts—an important question for the value of permits already in hand.

Wisconsin supplied a different form of constraint. Wisconsin Watch reported that Oracle voluntarily dismissed its challenge to credit requirements for major We Energies data-center customers. The A- credit threshold and collateral obligations for lower-rated developers remain in force, while the Port Washington campus also faces a restarted transmission-line and substation application process. The result is that financial security and physical grid connection remain separate, necessary hurdles for the project.

Local resistance continued to produce practical consequences rather than just public criticism. NC Newsline reported that a developer withdrew a Raleigh proposal after organized opposition, while Greensboro, Yadkin County, and Alamance County were considering temporary pauses on new data-center development. In Maysville, Kentucky, farmers rejected roughly $26.48 million in offers for land proposed for an AI data-center project, which is also being challenged in court. The developer has not been publicly identified, and a reported Meta connection remains unconfirmed.

Key Points

  • The Ohio arrangement suggests that the central challenge for the largest AI campuses is no longer merely raising capital. It is making power delivery financeable over a long enough period for developers, tenants, equipment suppliers, and utilities to accept one another's exposure. Lease guarantees and grid-investment commitments are becoming as consequential as land acquisition.
  • Wisconsin's credit rules show how regulators are beginning to assign the downside of large-load infrastructure explicitly. Requiring collateral from weaker-rated customers is designed to keep unrecovered generation and network costs from falling on ratepayers if a project fails or changes course. That can protect customers, but it also makes a developer's balance sheet part of the interconnection timetable.
  • The local pattern seen in recent briefings is persisting, but it remains jurisdiction-specific. Raleigh's withdrawal is a concrete outcome; the North Carolina pauses are still under consideration; Nashville's dispute is now litigation. Taken together, they show that opposition matters most when it reaches a formal development gate—applications, permits, incentives, land control, or court action.
  • The more revealing point is that advanced approvals do not necessarily end local risk. Nashville's case suggests that permitting can become the beginning of a legal contest when cities later alter their view of a project's land-use or infrastructure consequences.

Implications

For developers and investors, a credible project case increasingly needs to show not only projected demand and site control, but also who carries the risk of utility upgrades, delayed energization, and a tenant's long-term payment obligations.

For utilities and regulators, the Wisconsin outcome preserves a model in which the financial readiness of a large customer is reviewed alongside the engineering readiness of its connection. Other jurisdictions may face similar pressure as proposed loads grow faster than transmission and generation can be delivered.

For communities, the Raleigh withdrawal and Nashville litigation illustrate two very different sources of leverage: opposition can halt a proposal before a vote, while disputes over already-issued approvals can move into costly and lengthy legal proceedings. Developers seeking speed will need local legitimacy early, not only after permits are filed.

Watchpoints

Watch

Whether definitive lease, financing, generation, and interconnection agreements for the Ohio campus are executed, and whether its first 2028 capacity phase remains credible as transmission and generation plans advance.

Watch

Metro Nashville's legal response and any early court decision on DC BLOX's claimed permits, vested rights, and the city's authority to restrict or acquire the project site.

Watch

How Oracle meets Wisconsin's collateral requirements, and whether the restarted transmission and substation applications alter the Port Washington campus timetable.

Watch

Whether North Carolina localities adopt the proposed pauses, and whether Indiantown's Aug. 18 council election changes the political path for its proposed hyperscale projects.

Fallout

Large U.S. data-center development is becoming more conditional on financeable power infrastructure and locally defensible approvals, though the constraints remain uneven across projects and jurisdictions.

Final Thought

Yesterday did not show an industry-wide retreat from AI infrastructure. It showed the harder reality beneath the capacity announcements: the projects moving forward are those that can turn demand for compute into bankable power, permits, and public legitimacy.