Plain-English framing. KKR is one of the three largest US private-equity firms by AUM (~$600B). KIA (Kuwait Investment Authority) is one of the older sovereign wealth funds (~$800B) and a frequent KKR LP. Vistra is the largest competitive power producer in Texas and one of the largest gas-and-nuclear generation operators in the US. NVIDIA is the dominant AI chip supplier. The four-way structure — sponsor + LP + power asset + chip supplier — is a closed-loop financing-and-supply stack designed to remove every external dependency hyperscalers currently navigate site-by-site. What 'integrated coordination point' actually means. The Helix press materials describe four functions: (1) site identification and acquisition; (2) power-purchase agreements (Vistra) and on-site generation financing; (3) data-center campus construction (sponsor capital, hyperscale lease-up); (4) connectivity (fiber, transmission interconnection). This is — explicitly, in their own framing — the integrated site readiness layer. Adam Selipsky's prior role running AWS (where he was responsible for AWS's $80B+ infrastructure spend) is the credentialing signal that hyperscalers will return calls. What's NOT in the offer. Helix is positioned to serve hyperscalers — the seven names that command the colocation market. It is not (at $1B+ minimum check sizes) serving the mid-market AI-factory developers (Applied Digital tier), enterprise colos, or the regulatory-research workflow itself. It is also not building an LLM-ingested regulatory knowledge graph; its competitive edge is capital + AWS-customer-relationship + Vistra-baseload, not docket-tracking. So Cliff's narrowest survival positioning is the layer Helix is buying its way OUT of: the unstructured regulatory work itself, sold to the developers Helix isn't taking on as customers (mid-market and smaller hyperscalers, plus the consulting firms that serve them).
Primary source · KKR press release / Yahoo Finance / Bisnow / HPCwire ↗
Why it matters
Three pressure-test questions Helix forces Cliff to answer this week, in order of urgency. (1) Does the 'site readiness OS' positioning hold once Helix exists, or does Cliff need to narrow further to 'regulatory and docket intelligence inside the site readiness OS, sold to the developers Helix doesn't cover'? The strategy/competitive-landscape-and-adjacencies.md framing already implies the narrower version — Helix makes it required. (2) Is the consulting-firm channel still a wedge, or do the AmLaw 100 land-use practices and Trinity-tier engineering consultants get rolled into Helix's tuck-in stack within the next 18 months? If they do, Cliff's enterprise-sales motion needs to start before Helix's M&A motion does. (3) The Adam Selipsky signal: when a $10B vehicle hires a former AWS CEO to run hyperscaler relationships, that means the hyperscalers want a single integrated counter-party, not 19 best-of-breed vendors. Cliff's path to a hyperscaler relationship — which Tamir Mengesha / QTS, Smarak Bhuyan / Google have hinted at separately — needs to be through the regulatory-knowledge-graph product specifically, not 'we do site readiness too.' Worth a focused strategy memo before next week's PUCT / FERC density obscures it.
Related filings
Oracle sued Wisconsin PSC Jun 19 Ozaukee County / challenging April tariff rule / $100M/year financial security / very large customer >20 MW sub-A credit / Oracle BBB / Port Washington $15B 672 acres 1 GW 4 buildings We Energies / statutory-authority + discrimination + due-process theories / parallel administrative reconsideration / first hyperscaler-vs-PSC ratepayer-protection lawsuit / template for VA SCC MD FERC IL DCIP TX SB6 / AWS BBB+ adjacent risk / expected 6-12 months to ruling
Plain-English background on why this lawsuit matters more than a single facility dispute. Multiple states have enacted or are enacting 'ratepayer protection' rules for hyperscaler-scale customers in 2025-2026: Virginia's SCC rate class (approved Nov 2025,...
ERCOT Batch Zero / PCLR / NPRR1325 PGRR145 / PUCT approved Jun 18 / effective Jul 10 / DSP TSP applications due Jul 10 / ERCOT submission Jul 24 / classification notices Aug / final transmission plan Fall 2027 / Batch 1 opens Summer 2027 / first formal large-load interconnection track in Texas
Plain-English background. ERCOT (Electric Reliability Council of Texas) runs the Texas grid that covers about 90% of the state's load — everything except a few corners that sit on SPP or Eastern Interconnection. ERCOT is unique among US grid operators because...
FERC show cause orders Jun 18 / Section 206 / PJM MISO SPP CAISO ISO-NE NYISO / 30-day informational report Jul 20 / 60-day tariff response Aug 17 / 90-day abeyance request Aug 3 / five reform categories / cost-shift prevention is the big one / colocation + BTMG rules / flexible-load transmission services
Plain-English version. On June 18, 2026, the Federal Energy Regulatory Commission (FERC, the federal regulator with jurisdiction over the interstate transmission grid) used Section 206 of the Federal Power Act to issue what are called 'show-cause orders'...
Abbott directive Jun 10 / PUCT + ERCOT memo due Jul 17 / residential transmission cost reduction by Jul 31 / data centers self-fund infrastructure / TX legislative agenda preview / context for Kilby
Plain-English version of what Abbott actually directed. On June 10, 2026 — twelve days before the Project Kilby announcement — Texas Gov. Greg Abbott sent a formal directive letter to the Public Utility Commission of Texas (PUCT, the state utility regulator)...