What Developers Need to Get Right Before Selling Spare Capacity to AI Operators

A new line item is starting to show up in multifamily pro formas, and it is not a tenant amenity. Developers are installing enterprise GPU hardware in or on their buildings and selling the building’s spare electrical capacity, and the compute that capacity produces, to a third-party operator tied to the AI buildout. On April 14, 2026, SPAN announced XFRA, a “distributed data center” product built on exactly this premise: a network of compute nodes placed at residential and small-commercial sites, each node a liquid-cooled server carrying sixteen NVIDIA RTX Pro 6000 Blackwell GPUs that runs whenever the host’s panel has headroom. The first proof-of-concept, one hundred nodes in new PulteGroup homes, is slated for the third quarter of this year. The branding varies, from “AI nodes” to “edge compute” to “distributed data center,” but the deal underneath is the same, and it is coming to apartment portfolios next.

The economic logic is hard to argue with. Grid interconnection queues in the major data-center hubs now run four to seven years, and power, not land or capital, has become the binding constraint on new AI capacity. A building already has a service connection and unused load behind it. If you can monetize that headroom, you are selling something the market is desperate for without waiting in anyone’s queue. The International Energy Agency projects data-center electricity use roughly doubling to about 945 TWh by 2030, with the United States accounting for the largest share of the increase. That demand has to land somewhere, and “somewhere” increasingly includes buildings that were financed, zoned, and insured as housing.

That last clause is where I enter the fray. This piece walks through the three questions under Texas and Missouri law: whether the use is permitted, whether you are about to become a regulated utility, and what your existing loan already lets you do with the building and the money or what you need in your loan documents to allow this buildout.

Question one: is this a permitted use?

Start with the most basic point, because it is the one most likely to be skipped on a deal moving fast. A multifamily building sits in a district that was zoned for residential use. Running a commercial data-processing operation that sells output to an outside company is not a residential use, and in most ordinances it is not an enumerated permitted use in a residential or multifamily district either.

Texas has no statewide zoning; land-use control is delegated to municipalities. A home-rule city’s authority to separate “business, industrial, [and] residential” uses and to confine each to its own district runs through Chapter 211 of the Local Government Code. Tex. Loc. Gov’t Code §§ 211.003, 211.005. Whether a given ordinance permits commercial compute in a multifamily district is therefore a city-by-city question, and in most cities it does not. That leaves the developer to argue the installation is an accessory use subordinate to the housing, or to seek a specific-use permit, variance, or rezoning. Houston is the well-known asterisk: with no comprehensive use-zoning, the binding constraint there is far more likely a recorded restrictive covenant or the project’s own financing and condominium documents than a use district.

Missouri’s enabling statute is more centralized but lands in the same place. Cities zone under Chapter 89, which authorizes regulation of “the location and use of buildings, structures and land for trade, industry, residence or other purposes” and requires that zoning follow a comprehensive plan keyed to “the character of the district and its peculiar suitability for particular uses.” RSMo §§ 89.020, 89.040. Missouri zoning is permissive by district: a use is lawful only if the ordinance lists it for that district. A commercial compute enterprise selling to a third party will rarely be on the residential list, so the owner is back to a conditional-use permit, variance, or rezoning under §§ 89.060 and 89.080–.090. Missouri’s home-based-work statute, RSMo § 89.500, does not rescue this. It protects a resident’s own occupation, not a building-wide commercial installation selling capacity to an outside operator.

Do not assume a nonconforming-use argument fixes the problem. That doctrine protects only a use that lawfully existed before the restriction took effect; a commercial use newly dropped into a residentially zoned building is simply unlawful, not “grandfathered.” Missouri states the rule cleanly: nonconforming protection attaches only to a use predating the ordinance and is lost on abandonment. See State ex rel. Capps v. Bruns, 353 S.W.2d 829 (Mo. App. 1962). A freshly installed node array has nothing to grandfather.

The consequences of getting this step wrong or hand-waving at it are large. Almost every loan document carries a representation and covenant that the property complies with applicable law and zoning, and many separately bar changing the use or operation of the property without lender consent. An unpermitted commercial use can put you in default of your own loan on the strength of the very revenue you installed the equipment to earn, and it can foul up the title, casualty, and condemnation picture later. An unpermitted commercial use may also put your certificate of occupancy in jeopardy.

Why would anyone find out? Well, that is not a question we should be answering as developer counsel, but it is practical. I would argue that AI and data-centers are at the center of high emotions and because of those emotions cities may be willing to look harder to regulate their use and adjacent uses like the one proposed in this article. In short, developers will have a target on their back so you need to get this question right and early.

Question two: are you accidentally becoming a utility?

There is a world of difference between selling compute and selling power, and the deal documents have to land cleanly on one side of that line. In Texas’s competitive market, a person may not “provide retail electric service” unless certified by the Public Utility Commission as a retail electric provider. Tex. Util. Code § 39.352; 16 Tex. Admin. Code § 25.107 (certificate required before “purchasing, taking title to, or reselling electricity to provide retail electric service”). The apartment submetering regime is a narrow exception built for one thing: passing electricity through to residential tenants at cost. The rule is explicit that an owner “shall not impose any extra charges on the tenant over and above those charges which are billed by the retail electric provider or utility to the owner.” 16 Tex. Admin. Code § 25.142; see also Tex. Util. Code ch. 184. A third-party AI operator is not a residential dwelling-unit tenant, and selling capacity to it at a margin is the opposite of an at-cost pass-through. Sell the power to that operator and you risk being characterized as an uncertificated retail electric provider. Sell the compute output, a service the owner produces using power it consumes, and you are on far safer ground.

Missouri reaches the identical fault line through its definitions. A “public utility” subject to Public Service Commission jurisdiction includes any “electrical corporation,” RSMo § 386.020(43), but the definition of electrical corporation carves out a producer that generates or distributes electricity on private property “for its own use or the use of its tenants and not for sale to others.” RSMo § 386.020(15). The whole exception turns on those last four words. Supplying your own tenants is not being a utility; selling to a non-tenant third party for gain is where PSC jurisdiction starts to attach. Missouri has also just legislated directly at this demand: effective August 28, 2025, RSMo § 393.130.7 requires large utilities to file special tariff schedules for customers projected to draw 100 MW or more (50 MW for smaller utilities), so that hyperscale loads “reflect the customers’ representative share of the costs incurred to serve” them rather than shifting cost onto everyone else. The state is watching large compute load closely, and structuring around it through a residential building does not make the load invisible.

The drafting takeaway is the same in both states. The owner should be selling a compute service and consuming the electricity itself; the operator should take any electric service it needs directly from a certificated provider or the serving utility. If the papers instead read like the owner is metering and reselling kilowatt-hours to the operator at a markup, the owner has wandered into regulated territory in both Texas and Missouri.

Question three: what does your existing loan already control?

Assume the use and utility questions are handled and real money now flows. Before you treat it as free cash flow, or pledge it to finance the hardware, look at what your mortgage lender already controls.

A deed of trust assigns rents and leases: consideration for the use or occupancy of real property. Your compute-hosting revenue is not naturally rent. It is payment for a service (compute) and for energy, which Article 9 treats as personal property. Both states define “account” to include a right to payment “for services rendered or to be rendered” and, tellingly for this fact pattern, “for energy provided or to be provided.” Tex. Bus. & Com. Code § 9.102; RSMo § 400.9-102. Revenue styled as a pure contractual share is a payment intangible or general intangible. Either way it is Article 9 collateral, reached by a UCC-1 financing statement.

That distinction cuts in both directions, and you need to know which way it runs before you sign. If your loan documents include a security agreement granting a security interest in “accounts,” “general intangibles,” and after-acquired property, backed by a filed UCC-1, your lender’s lien sweeps the new revenue automatically as it arises, and you are not free to pledge it to an equipment or revenue financier without tripping a negative-pledge covenant. Tex. Bus. & Com. Code §§ 9.204, 9.315; RSMo §§ 400.9-204, 400.9-315. If instead your collateral package is real-property-only, just a deed of trust and a bare assignment of rents with no UCC-1 on accounts, the compute revenue may sit outside your lender’s collateral. That gives you room to finance the hardware separately, but it does not mean your lender has blessed the arrangement; a financier you bring in could prime on a first-to-file basis, and your loan’s other covenants still apply. Tex. Bus. & Com. Code § 9.322; RSMo § 400.9-322. (Missouri adds a wrinkle on the real-property side: a collateral assignment of rents is generally not self-executing, so a lender must take an affirmative step, such as possession, demand, or a receiver, to reach even genuine rents.)

The practical move is the same whichever way it comes out: read the loan before you sign the hosting agreement. Most modern loan documents require consent for a change in use or operations and prohibit additional liens, so you may need your lender’s sign-off no matter how the collateral question resolves. It is far cheaper to ask up front than to explain it after a servicer’s monitoring call flags new revenue on the property.

Texas and Missouri at a glance

Question	Texas	Missouri
Zoning authority	No statewide zoning; municipal, via home-rule/general-law cities. Tex. Loc. Gov’t Code §§ 211.003, 211.005. Houston has no use-zoning; covenants control.	Municipal, under Chapter 89; permissive-by-district. RSMo §§ 89.020, 89.040. County zoning under ch. 64.
Commercial compute in a residential district	Generally not a permitted use; needs SUP, variance, or rezoning.	Generally not a permitted use; needs CUP, variance, or rezoning under §§ 89.060, 89.080–.090.
Nonconforming use	Protects only pre-existing lawful uses; a new install does not qualify.	Same; protection lost on abandonment. Capps v. Bruns, 353 S.W.2d 829.
Reselling power to a third party	Risks unauthorized “retail electric service.” Tex. Util. Code § 39.352; 16 TAC §§ 25.107, 25.142 (no markup on submetered power).	Risks becoming an “electrical corporation/public utility”; tenant carve-out is “not for sale to others.” RSMo § 386.020(15), (43).
Large-load regulation	Competitive ERCOT market; PUCT rules in 16 TAC ch. 25.	New large-load tariff statute, RSMo § 393.130.7 (eff. 8/28/2025), 100 MW / 50 MW thresholds.
New revenue as collateral	”Account” includes payment “for energy provided.” Tex. Bus. & Com. Code § 9.102; after-acquired and proceeds, §§ 9.204, 9.315; priority, § 9.322.	Same UCC text. RSMo §§ 400.9-102, 400.9-204, 400.9-315, 400.9-322. Assignment of rents not self-executing.

So why might this be fine?

This is really, really cool and we do not often get cool things in real estate development. None of these issues is a prohibition; each is a structuring problem with a known solution. Zoning is local. In a permissive jurisdiction, a city eager for the tax base and the “innovation” headline may well grant a specific-use permit, and in Houston the use-district objection largely evaporates. The utility risk is avoidable by design: if the owner sells compute as a service and consumes its own power, and the operator contracts directly for any electric service it needs, neither the Texas REP regime nor Missouri’s “for sale to others” line is triggered. The loan question is usually a matter of asking rather than litigating. Lender consent to a well-structured compute deal is obtainable, especially where the revenue improves debt-service coverage. And the underlying demand is not a fad. The interconnection bottleneck is structural, the IEA’s load projections are enormous, and a building with spare capacity is genuinely valuable. A developer who papers the deal carefully, with permitted use confirmed, the sale structured as compute rather than power, and lender consent in hand, can capture a revenue stream the market is scrambling for.

Citations

Cases

State ex rel. Capps v. Bruns, 353 S.W.2d 829 (Mo. App. 1962) (nonconforming use protected only if it lawfully predated the restriction and was not abandoned).

Statutes and Regulations

Tex. Loc. Gov’t Code § 211.003 (municipal zoning authority over use of buildings and land).

Tex. Loc. Gov’t Code § 211.005 (zoning districts; uniformity within a district).

Tex. Util. Code § 39.352 (certification required to provide retail electric service).

Tex. Util. Code ch. 184 (submetering of utility service in apartment houses).

16 Tex. Admin. Code § 25.107 (REP certificate required before purchasing, taking title to, or reselling electricity for retail service).

16 Tex. Admin. Code § 25.142 (apartment submetering; owner may not charge tenants above the provider’s charges to the owner).

Tex. Bus. & Com. Code § 9.102 (definitions; “account” includes a right to payment for services rendered and “for energy provided or to be provided”).

Tex. Bus. & Com. Code § 9.204 (after-acquired property; future advances).

Tex. Bus. & Com. Code § 9.315 (security interest in proceeds; continued perfection).

Tex. Bus. & Com. Code § 9.322 (priority; first to file or perfect).

RSMo § 89.020 (city zoning enabling act; regulation of use of buildings and land).

RSMo § 89.040 (zoning in accordance with a comprehensive plan; character of the district).

RSMo §§ 89.060, 89.080–.110 (rezoning, board of adjustment, variances, certiorari review).

RSMo § 89.500 (home-based work; limited protection for a resident’s own occupation).

RSMo § 386.020 (definitions; “electrical corporation,” subsec. (15), with tenant carve-out “not for sale to others”; “public utility,” subsec. (43)).

RSMo § 393.130 (safe and adequate service; just and reasonable rates; subsec. 7 (eff. Aug. 28, 2025) large-load tariff requirement at 100 MW / 50 MW thresholds).

RSMo § 400.9-102 (definitions; “account” includes payment “for energy provided or to be provided”).

RSMo § 400.9-204 (after-acquired property; future advances).

RSMo § 400.9-315 (rights in proceeds).

RSMo § 400.9-322 (priority among conflicting security interests).

Secondary Authority

SPAN, SPAN Announces XFRA, a Distributed Data Center Solution to Close the Speed-to-Power Gap for AI Compute Demand (Apr. 14, 2026), https://www.span.io/blog/span-announces-xfra-a-distributed-data-center-solution-to-close-the-speed-to-power-gap-for-ai-compute-demand (XFRA node hardware, PulteGroup proof-of-concept, deployment timeline).

Span and Nvidia to Develop AI Data Centers in Your Backyard, pv magazine USA (Apr. 15, 2026), https://pv-magazine-usa.com/2026/04/15/span-and-nvidia-to-develop-ai-data-centers-in-your-backyard-lowering-electric-bills/.

Span Wants to Turn Homes Into Mini Data Centers, Scientific American, https://www.scientificamerican.com/article/span-wants-to-turn-homes-into-mini-data-centers/.

International Energy Agency, Energy and AI: Energy Demand From AI (2025), https://www.iea.org/reports/energy-and-ai/energy-demand-from-ai (data-centre electricity consumption projected to roughly double to about 945 TWh by 2030; United States the largest share of the increase).

Lawrence Berkeley National Laboratory, Queued Up: 2024 Edition (interconnection queue volumes), https://emp.lbl.gov/queues; RMI, The Interconnection Queue Continues to Be a Barrier to U.S. Economic Competitiveness, https://rmi.org/interconnection-reform-ai-data-centers-generator-queues/ (multi-year interconnection wait times in major markets).