How to Unmask the Shell Company Behind a Data Center
A project lands in your town under a code name — "Project Blue," "Project Rowan" — bought by an LLC no one has heard of. That anonymity is a strategy, not an accident. Here's the five-step method to find the hyperscaler actually behind it, worked through the real chain of shell companies that hid Amazon behind Tucson's Project Blue — and why naming them changes your leverage.
A proposal appears in your county under a code name — Project Blue, Project Rowan, Project Ludi — and the land is bought by a limited liability company no one has heard of, formed a few weeks earlier. You can't find out who is behind it, and that is not an accident. It is the plan.
Why they hide
Developers manage what they call "social license to operate" as a financial risk. A code name and a shell LLC buy time: they let a project lock in land, rezoning, and incentives before organized opposition can form around the name of a company people recognize. By the time "Project Blue" is revealed as a hyperscaler, the entitlements are often already granted.
The patterns, by operator
Anonymity has fingerprints. From our own site registry, the major operators each shell their land deals in recognizable ways — and knowing the family is often step zero:
- Google buys through land-acquisition shells named Jet Stream LLC and Sharka LLC — the same two names recur from The Dalles, Oregon to Northern Virginia.
- Meta rotates codename shells: Greater Kudu, Raven Northbrook, Stadion, Pinnacle Mountain, and Wobniar — which is "Rainbow" spelled backwards.
- Microsoft leans on project names and generic "Holdings LLC" entities, less consistently codenamed.
- xAI (Colossus) files through site- and retrofit-specific LLCs — the former Electrolux plant in Memphis is the known one.
- OpenAI–Oracle (Stargate) works through per-site developer LLCs like Crusoe and Lancium at Abilene, Texas.
If the LLC on your deed matches a name one of these companies has used elsewhere, you may already have your answer before you file a single request.
A worked example: how Amazon hid behind "Project Blue"
Tucson's Project Blue is the textbook case, because the layers eventually came apart in public:
- The land was purchased by Humphrey's Peak Property, LLC, which then assigned its rights to a second shell, Bobcat B1 LLC, before the deal closed on 290 acres.
- The named developer was Beale Infrastructure.
- The actual client was Amazon Web Services — a fact confirmed only when a Pima County non-disclosure agreement surfaced, an agreement to keep Amazon's identity secret for five years.
Two shell LLCs, a development company, and a hidden hyperscaler behind an NDA: that is the standard structure, not the exception. We documented the same pattern of one project wearing different faces for different agencies in Tucker County, West Virginia.
The five-step unmasking method
You can run most of this from a laptop before the next hearing.
1. Pull the deed. Your county recorder or assessor's property records name the LLC that bought or optioned the land. In most counties this is free and online. Note the sale date and the exact LLC name.
2. Look up the LLC. Search that name in your Secretary of State's business registry. You're after the registered agent, the organizer, and the formation date. A generic corporate agent (CT Corporation, a big law firm) and a formation date weeks before the land deal are both tells that this is a purpose-built shell.
3. Match the pattern. Hyperscalers reuse naming conventions, law firms, and site-selection consultants across projects. Cross-reference the LLC and its agent against our operator and site registry, which maps known operators to the shell entities and campuses they've used elsewhere.
4. Read the utility filings. The land deal may be anonymous, but the power isn't. Interconnection-queue entries and rate filings frequently name the load, its size in megawatts, or the consultant representing it — even when the deed does not.
5. Request the development agreement and any NDA. The public body negotiating tax incentives holds the documents — including, as in Tucson, the agreement specifying who they promised to keep secret. A public-records request is the single highest-leverage step; the hearing-prep questions page has language you can adapt.
Why it's worth the effort
You cannot negotiate with a shell company. Putting the real name on the project changes everything: it tells you the true power and water demand, it gives you the corporate climate and community commitments you can hold the company to, and it reveals what that operator has already conceded to other communities.
Los Lunas, New Mexico is the proof. When the village traced Greater Kudu LLC back to Meta, it didn't just win a name — it negotiated a water agreement with real teeth: up to 3 million gallons a day, automatically suspended in a declared Stage 3 water emergency, plus Meta funding for Rio Grande watershed restoration worth roughly 172 million gallons a year. You cannot get a clause like that from "Greater Kudu LLC." You get it from Meta. Anonymity is leverage — for them. Naming them takes it back.