Scrutica
Power
Supply Chain
Not yet available
Facility-level telemetry including power capacity, hardware deployments, supplier relationships, and downstream dependencies. Linked to Humain with cross-referenced BIS Entity List matches.
Detailed intelligence on HUMAIN Riyadh Phase 1. Operational capacity and ownership structure are mapped to determine the facility's strategic position within the global AI supply chain (including its exposure to relevant export control restrictions).
As of 2026-05-16
Direct operator or owner of this facility per the Scrutica facility record.
Ownership chain not yet documented in the available data (PitchBook affiliate graph, FactSet supply graph, SEC filings, LEI registry; as of 2026-05-16). The chain may extend further once additional ingestion runs complete; absence here reflects coverage at this snapshot, not a documented apex.
No jurisdictions documented for this chain in the available data — at least one ancestor must carry an HQ country in the canonical organization record for jurisdictional exposure to compute. This section will populate automatically as additional ingestion adds HQ countries to the chain.
Description
HUMAIN Phase 1 Riyadh site is one of two 100 MW campuses (Riyadh + Dammam) announced 2025-05-13 under HUMAIN's NVIDIA partnership. Phase 1 deployment target: 18,000 NVIDIA GB300 Grace Blackwell GPUs across the partnership (split across both campuses), part of a 500 MW / "several hundred thousand GPU" 5-year roadmap. HUMAIN is the PIF-owned national AI infrastructure subsidiary. Ground broken 2025; first operations targeted Q2 2026.
Timeline
Announced
May 13, 2025
Expected Operational
Jun 30, 2026
Notes
100 MW per-campus figure from secondary press (Al Arabiya 2025-08-26, DCD 2025-08); NVIDIA primary announcement discloses only the 500 MW 5-year aggregate. authority_tier=2 reflects the press-tier per-campus split. Exact Riyadh address not yet disclosed — lat/lng left null. GB300 split between Riyadh and Dammam not separately disclosed.
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-05-16. 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 PitchBook deal records (M&A, buyout, divestiture, asset sale, JV formation); PitchBook 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. PitchBook LP-disclosure rate is partial; absence of evidence here is not evidence of absence.
The walk for HUMAIN Riyadh Phase 1starts 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 > FactSet Workstation / Revere > Compustat > BIS / Federal Register > PitchBook). 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 (PitchBook): 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 PitchBook'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 PitchBook 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-05-16. Walk depth observed: 1 hop. Sources combined: Scrutica facility record + PitchBook affiliate graph + SEC CIK cross-reference + LEI registry + (where applicable) FactSet Revere supply-chain graph + Federal Register designation closures.