Scrutica
Capacity, hardware inventory, ownership chain, and supply-chain position for Meta Temple. Any export-control exposure is walked through the canonical organization graph — surfacing when the BIS Entity List touches a node above the facility in the chain — rather than asserted at the facility row.
As of 2026-07-27
Operator (or owner of record) per the Scrutica facility row.
2 records
Every organization on record at Meta Temple, with the role it plays and the source for that specific claim. A party marked inferred is recorded as a reading of the cited source rather than something the source states outright.
Description
Meta Temple is notable for a mid-flight change in construction. A traditional H-shaped Meta data center was partially built on the site by 2023, only to be demolished in favor of Meta's new AI-optimized data center design. The power capacity of the new design was reported by construction company JE Dunn, and is backed up by our cooling model. Later, a third data center building was added to the plan. Compute capacity assumes that NVIDIA GB300 NVL72 servers are used, as these are the most popular
Notes
Total capital cost (2025 USD): $5.76B | Epoch estimation methods: our cooling equipment power model, company disclosures, chip availability, chip efficiency.
Other Meta Platforms, Inc. Facilities
source_url_contains_claim_verifiedduplicate_name_ambiguous_same_site — Meta Temple: the named 4.6x capacity contradiction (152 MW operational, epoch-ai vs 700 MW announced, wrds-ciq-keydev). wrds-ciq row has no coordinates; owners differ (org-meta vs wrds-ds-borr-meta, an unresolved borrower-entity alias). Genuinely unresolved -- likely a construction-phase or a related-but-distinct project, not a simple duplicate. Cross-flag per the Jamnagar template, do not merge or pick a capacity figure.Chain terminates at a publicly-listed entity (Meta Platforms, Inc.). Subsequent ownership is observable via SEC filings or the equivalent national registry.
United States (US)
Operates the Export Administration Regulations (EAR) and the BIS Entity List under 15 CFR 730–774; deemed-export rules extend reach to foreign nationals on US soil.
Regimes: Wassenaar Arrangement; US EAR (BIS Entity List authority)
Established via: Meta Platforms, Inc.
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-07-27. Cascade closures evaluated: 0.
No ownership-change events documented in the available data for any entity in this chain over the last 5 years. Events draw from a licensed corporate-ownership database’s deal records (M&A, buyout, divestiture, asset sale, JV formation); coverage is strongest for private US/EU transactions and partial for state-owned-enterprise restructurings or non-Western private deals. Subsequent ingestion runs may add events here.
No documented sovereign or state-linked LP investment touches any entity in this chain. The licensed database’s LP disclosure is partial — an empty list here is a coverage limit, not a finding.
The walk for Meta Templestarts at the operator org id (or owner org id when no operator is recorded) and climbs upward through the unified affiliate graph, normalized to trace child-to-parent relationships. At each hop, the highest-authority parent edge wins (priority ordering: SEC EDGAR / 10-K / LEI registry > licensed corporate-ownership database > licensed supply-chain database > BIS / Federal Register > licensed affiliate graph). Confidence and recency break ties.
The walk terminates on (a) a node with a public-filing-grade ancestor edge — a SEC filer, an LEI-registered listed entity, or a 10-K-disclosed parent — (b) a government entity, (c) a 10-hop limit, or (d) a detected cycle. When termination is not at a public filer or government, the panel labels the chain's end-state as opaque beyond that point. Opacity is reported, never implied.
Per-source confidence (licensed corporate-ownership database): HIGH for Parent / Subsidiary edges; MEDIUM for JV and AFFILIATE edges. Known limitations: (1) shell companies with undisclosed principals terminate the public-record walk; (2) recent transactions reach the panel after the database's weekly refresh; (3) cross-jurisdiction private holding structures may carry intermediate hops that are not in any ingested source. Each row carries an edge-level as of date so freshness is auditable per hop.
Two further caveats are inherent to how the walker and the underlying data compose. The walker selects a single highest-authority parent per hop, so JV or multi-parent ownership structures collapse to one displayed path; alternate parents exist in the ingested sources but are not surfaced on this card. And some licensed-database edges encode parent-of relations against entity-resolved stub IDs whose display name reflects a sub-entity (a business unit, an acquired-then-renamed line) rather than the canonical parent — when a chain reads structurally surprising, the per-row source citation is the authoritative reference, not the chain's narrative shape.
Computed at: 2026-07-27. Walk depth observed: 1 hop. Sources combined: Scrutica facility record + licensed corporate-ownership database + SEC CIK cross-reference + LEI registry + (where applicable) licensed supply-chain database + Federal Register designation closures. The licensed databases are held under subscription and not redistributed; per-hop labels name no vendor.
Meta 100k
US