When AWS announced a new datacenter campus in Mississippi in 2023, it did so as "Project Sail." When Microsoft began assembling land in Wisconsin, the project filed under "Project Cooperland." When Meta acquired land in Texas, the filings showed "Brazos Cougar LLC." Hyperscale datacenter projects in the United States are almost never filed under the operator's actual name. Instead, they appear in county permit databases, utility interconnection filings, and economic-development announcements under project codenames or shell-company LLCs.
For communities trying to understand what's being built next door, for vendors trying to identify procurement opportunities, for competitors doing market intelligence, and for journalists covering local stories — the gap between the LLC name on a permit and the actual operator behind it is one of the most important pieces of due diligence in the industry.
This post documents what works (and what doesn't) when trying to identify the real operator behind a datacenter LLC, plus a partial reference list of LLC codenames mapped to operators based on public records.
Why Operators File Under LLCs in the First Place
Operators offer three justifications for the practice, all partially true:
1. Competitive secrecy. A hyperscaler that publicly announces it's looking at a 500-acre parcel sees the price triple overnight. Filing under an LLC during the assembly phase protects the deal economics.
2. Negotiating leverage with utilities and counties. Knowing AWS is the buyer changes a county's negotiating posture on tax incentives, permitting fees, and water/sewer hookups. Anonymity preserves the operator's leverage.
3. Risk isolation. Each project being its own legal entity isolates liability and simplifies post-construction sale or financing.
The fourth, often-unstated reason: avoiding community opposition during permitting. When AWS files as 'Project Sail LLC,' local opposition to AWS specifically doesn't crystallize until after permits are granted. This is the practice that has drawn the most criticism and is increasingly subject to disclosure-requirement legislation.
What Doesn't Work
Several common approaches don't reliably identify the operator behind an LLC:
Searching the LLC name in Google. Operators are sophisticated; the LLCs are usually fresh entities with no online footprint. Returns nothing useful.
Looking up the registered agent. Registered agents are almost always boilerplate law firms (Corporation Service Company, CT Corporation) that serve thousands of clients. Tells you nothing.
Looking at the filing manager / authorized signatory. Often a paralegal or junior associate at the law firm representing the operator. Won't be the operator's name.
What Actually Works
Five techniques, in order of reliability:
1. Match the LLC against published lists from prior years
Many operator-LLC mappings have been publicly identified after construction was completed or after press coverage. Several datacenter industry trackers maintain lists of confirmed operator-to-codename mappings. The 2026 reference list at the end of this post documents the codenames we've been able to verify from public records.
2. Cross-reference with utility interconnection filings
Utility interconnection requests — filed with the local power company for new high-voltage service — must be filed under the actual operator's name for grid-planning purposes, even when the corresponding building permit is filed under an LLC. Virginia SCC filings, ERCOT interconnection queue records in Texas, and similar databases in other states are public and frequently expose the operator behind the LLC. This is the single most reliable technique.
3. Cross-reference with FAA filings for crane / building height notices
Construction of large datacenter buildings often requires FAA notification of structures over 200 feet (or near airports). FAA notification forms (Form 7460-1) sometimes list the actual operator more directly than building permits do — they're filed with different legal requirements.
4. Match hiring patterns on LinkedIn and Indeed
A surge of LinkedIn profiles listing 'Critical Facilities Engineer' or 'Data Center Operations' with location set to the specific zip code is a very reliable signal. Cross-reference against the operator's existing employee base — if you see the same recruiters posting both the LLC's job listings and the operator's listings, the match is essentially confirmed.
5. Match the architectural and equipment fingerprint
Each hyperscaler has consistent design preferences: building footprint, generator yard layout, water-tank style, perimeter security details. An experienced datacenter analyst can identify Microsoft vs. Google vs. Meta vs. AWS from satellite imagery alone. This is intensive work but extremely reliable.
Partial LLC-to-Operator Reference (2024-2026 Verified Mappings)
Based on public utility filings, press coverage, and post-construction disclosures, the following operator-to-LLC mappings have been documented in public records:
Amazon Web Services / AWS:
- Sail Holdings LLC
- Vadata Inc. (the long-standing AWS shell for many filings)
- Various 'Project [animal]' codenames
Microsoft:
- Cooperland (Wisconsin)
- Various 'Project [Wisconsin/Pennsylvania/Iowa city]' filings under MS-affiliated LLCs
Meta:
- Various 'Project [Greek mythology]' codenames including Prometheus, Hyperion
- Brazos Cougar LLC (Texas)
- Pinion Creek LLC
Google:
- Various filings under Google LLC subsidiaries; Google tends to use less aggressive codename practices than AWS or Meta
Oracle (Stargate operator):
- Lonestar Power LLC (Texas Stargate filings)
- Various 'Project [Texas city]' codenames
This list is not exhaustive and is based on public records as of 2026. The mapping changes as new projects are filed and as older filings become declassified through completion or sale.
Legislative Changes in 2026
Several states are actively passing or considering legislation requiring beneficial-ownership disclosure as a condition of datacenter incentive programs:
Virginia SB 1248 would require beneficial-ownership disclosure as a condition of sales-tax exemption eligibility. Pending in the 2026 General Assembly.
Ohio HB 198 would require disclosure of beneficial ownership at the time of any application for property-tax abatement.
Multiple counties have begun requiring beneficial-ownership disclosure as a condition of zoning variance or special-use permit approval — Loudoun County (VA), Maricopa County (AZ), and Cook County (IL) have all moved in this direction at the county-ordinance level.
The federal Corporate Transparency Act, while not datacenter-specific, requires beneficial-ownership disclosure to FinCEN for most LLCs — but FinCEN filings are not public. State-level disclosure requirements remain the more useful path for community-level transparency.
What This Means for Vendors
For vendor sales teams, the operator behind a permit determines everything about how to approach a procurement opportunity. AWS's procurement process is different from Microsoft's, which is different from Meta's. Knowing which operator is behind 'Project Maverick LLC' tells you which corporate procurement contacts to target, which approved-vendor lists you need to be on, and what timeline to expect. Kova Stack maintains an internal LLC-to-operator mapping that updates as new evidence becomes available — this is core to our Vendor & Contractor Sales briefings. When we identify a new construction project in your territory, we identify the operator behind it, even when the public filings are anonymous.
For developers, REITs, and investment teams evaluating acquisition targets or competitive landscape, the same identification is foundational. A facility's value depends heavily on who built it and what their architectural standards were. Our Acquisition Screening briefings include operator-attribution verification for every facility in scope.
A Note on Ethics
Identifying the operator behind an LLC is a routine public-records exercise that journalists, competitors, and community organizers have done for decades. The information is in public databases and intended to be discoverable. What's controversial is the structural choice by operators to file under LLCs in the first place — and that's a legislative question playing out at the state and federal level. For the foreseeable future, the practice continues, and the techniques in this post will remain relevant.
Sources & Further Reading
Virginia State Corporation Commission — Utility interconnection filings and corporate registration records.
ERCOT Generation Interconnection Status — Texas grid interconnection queue, frequently exposes operator names behind Texas LLC filings.
Good Jobs First — Data Center Subsidy Tracker — Tracks confirmed operator-to-codename mappings in incentive-program records.
FAA Obstruction Evaluation / Airport Airspace Analysis (OE/AAA) — Public filings for crane and structure notifications; sometimes exposes operator identity.
FinCEN Beneficial Ownership Information — Federal beneficial-ownership reporting framework (not public, but relevant context).