Insight
Who the big players are (through the public record)
“Who’s big” is a category question, not a scraped league table. Watt Brief does not publish a proprietary MW market-share database. It tracks document moves: a named party, an applicant, a protester, a queue ID, a docket caption.
The same campus can wear more than one hat. A cloud major may appear as an 8-K registrant, a utility-docket protester, or a county applicant. A wholesale developer may be the name on the site plan while the operator is still blank. The weekday product is the identity of the paper, not a ranking of names.
Hyperscale owners / operators
Named parties in 8-Ks, utility dockets, county cases
Wholesale colo / developers
Permit applicants and interconnection-queue rows
Utilities / ISOs / PUCs
The paper Watt Brief reads every weekday
GC / MEP / transmission
Secondary: bid tabs, interventions, job clusters
Source: Watt Brief category map of how parties appear in public records — 8-Ks, county cases, interconnection queues, and utility/ISO/PUC dockets. Not a measured MW share and not a vendor list. How we key a row: Sources and the event identity builder.
Hyperscale owners / operators
Cloud majors show up when they are a named party. That can be an EDGAR 8-K that states interconnection, a capacity commitment, or a material campus; a state utility docket where they protest a rate or a large-load tariff; or a county case where they are the applicant or a listed protester. The public fact is the caption and the document ID — not a rumor that they “must be behind” an LLC.
How we read the 8-K half: Reading an 8-K for power.
Wholesale colo / developers
Developers and wholesale colo platforms usually appear first on permits and interconnection queues: a rezoning or PAD, a site plan, an SPEX, a queue row under a special-purpose entity. The named operator often lags the land entity. Treat the applicant on the packet as the identity until a later filing names someone else.
Where those rows live: Who’s building now and How to read an interconnection-queue row.
Utilities / ISOs / PUCs
These are the other “big players” Watt Brief actually reads every weekday. ERCOT large-load / LLI, PJM large-load / IRAS, SPP HILL, PUCT and SCC dockets, FERC 205 and 206 packages — the process paper that binds a campus before a ribbon. A utility or ISO is not a developer. It is the source that prints the ID.
Adapters and event classes: Sources. ISO paper that binds: FERC and ISO paper that binds.
GC / MEP / transmission — secondary signal
General contractors, mechanical-electrical-plumbing packages, and transmission interventions are a secondary signal. Bid tabs, docket interventions, and clustered job postings can confirm that a site is moving. They are not a MW ledger and not a reason to invent an operator. Keep them high-level: the weekday row still needs a public-record identity.
Build the identity string: event identity builder.
Charts and facts on this page use cited public sources or labeled educational heuristics. They are not legal, engineering, or investment advice, and not a comps book. Confirm every number on the issuing agency or laboratory copy. Contact hello@wattbrief.com.
Free charts and calculators. The weekday brief is still the product.