Scrutica
Power
Supply Chain
Not yet available
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by Reliance Industries; any BIS Entity List exposure is walked through the canonical org graph rather than asserted at the facility row.
Capacity, ownership chain, and supply-chain position for Reliance–Meta AI Data Center (Jamnagar), including any export-control exposure that surfaces when the BIS Entity List touches a node above the facility in the chain.
As of 2026-07-10
Operator (or owner of record) per the Scrutica facility row.
Description
Announced 2026-06-10 jointly by Meta and Reliance Industries Limited (RIL). Reliance builds and owns the facility; Meta leases capacity — "Reliance will build a data center with 168 MW capacity, which Meta will lease" (Meta newsroom, verbatim). Phase 1 delivers 168 MW with an option to scale. Located in Jamnagar, Gujarat (no more precise address disclosed). Powered by renewable energy and cooled using desalinated seawater per RIL's own release; Meta states it "will cover the full cost of the energy and water supporting the facility." Expected completion "within two years" of the June 2026 announcement (~2028) — no hard date disclosed by either party. Described as Meta's first built-to-suit India capacity. NOT a joint venture for the data-center asset itself (the separate Reliance-Meta JV is an unrelated enterprise-AI/Llama vehicle).
Timeline
Announced
Jun 10, 2026
Notes
DEDUP FLAG (unresolved, surfaced not silently ignored): a pre-existing Epoch-sourced row fac-epoch-gc-reliance-industries-supercomputer (Jamnagar, IN, 1000 MW, 450,000 GPUs, is_estimated=true, "chip count estimated from power capacity, chip type uncertain", source archive.ph/tTvHo) ALREADY EXISTS in this database and may or may not describe the same physical site/campus as this new 168 MW Meta-lease row. This session could NOT independently re-verify the archive.ph source (WebFetch tool cannot retrieve archive.ph/archive.today — same class of restriction as the documented web.archive.org block). Given the Epoch row's own notes read as a broad, speculative, power-derived estimate of Reliance's OWN AI-compute ambition (is_estimated=true, no named tenant, no primary citation of a specific deal) versus this row's tier-1-dual-confirmed, named, tenant-specific 168 MW lease deal, these are treated as DISTINCT records pending reconciliation — do NOT sum their power_capacity_mw/total_gpu_count in any aggregate without first resolving whether they overlap. Flagged for a future cross-reference pass. [staged-ingest-2026-07-10]
Other Reliance Industries Facilities
Other Facilities in IN
Chain terminates at a publicly-listed entity (Reliance Industries). 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: Reliance Industries
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-07-10. 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 fund/LP database’s LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for Reliance–Meta AI Data Center (Jamnagar)starts 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-10. 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.
AIRAWAT-PSAI Phase 2
34/B/1, IN