Scrutica
GPUs
Supply Chain
Not yet available
Power capacity, hardware inventory, upstream suppliers, and downstream customers for the row owned by EuroHPC JU; 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 HammerHAI, 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-18
Operator (or owner of record) per the Scrutica facility row.
Ownership chain not yet documented in the available data (licensed corporate-ownership database, licensed supply-chain database, SEC filings, LEI registry; as of 2026-07-18). The chain may extend further once additional ingestion runs complete; absence here reflects coverage at this snapshot, not a documented apex.
Description
HammerHAI ("HAMMER AI Factory") is Germany's EuroHPC AI Factory, coordinated by the High-Performance Computing Center Stuttgart (HLRS) in consortium with GWDG Göttingen, Leibniz Supercomputing Centre, Karlsruhe Institute of Technology, and SICOS BW. Contract to deploy signed 2026-03-16 (EuroHPC JU); system is HPE-built, 215 NVIDIA GB200 NVL-4 nodes (860 GPUs total, 2x NVIDIA Grace CPU + 4x NVIDIA B200 Blackwell GPU per node), plus 9 Axelera AI AIPU accelerator nodes, 10PB VAST Data storage, NVIDIA Quantum-X800 InfiniBand (800 Gbit/s) networking. Stated peak performance >15 Exaflops AI inference (FP8/sparse, vendor-stated). Delivery scheduled Q2 2026 per the EuroHPC JU contract-signing press release; operational target second half of 2026.
Notes
STAGED — NOT YET INGESTED (Task #37 scope session, 2026-07-17). Power capacity (MW) is NOT disclosed by any source found — do not populate; a separate, distinct HLRS project ('Herder', targeting 2027) has a published 8MW figure that must not be conflated with HammerHAI. expected_operational_date left NULL rather than populated with a coarse placeholder: the EuroHPC JU press release states delivery 'scheduled for the second quarter of 2026' and operation 'expected... in the second half of 2026,' which is a half-year-precision range, not a specific date — per DQP no-false-precision, null is correct until a more precise date is disclosed; do not backfill with an arbitrary day-of-month. total_gpu_count (860) is a primary-source hardware count (215 nodes x 4 GPUs/node), not a capacity estimate. Funding: EUR 55 million total, 50% EuroHPC JU (Digital Europe Programme) / 50% German federal and state sources — not represented as a facilities-table field per current schema; would need to route through compute_capacity_snapshots or a program-level record if funding-tracking is wanted at the facility level. PER-FIELD SOURCE ATTRIBUTION (merge-gate verification 2026-07-17): status, timeline, funding split, vendor (HPE), and architecture class are stated in the EuroHPC JU contract release at source_url; the hardware counts (215 GB200 NVL-4 nodes, 4x B200 + 2x Grace per node, total_gpu_count 860, 10 PB VAST DASE, Quantum-X800) are NOT in the JU release — they are stated on the operator's own system page, https://www.hammerhai.eu/system/ (tier 1, operator disclosure, accessed 2026-07-17), which also notes the 9 Axelera AIPU nodes carry a 2027 delivery expectation. Both sources primary. [sovereign-staged-2026-07-18]
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.
No flags found across the chain (BIS Entity List, designation-cascade closures, or compute-threshold reporting obligations) as of 2026-07-18. 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 HammerHAIstarts 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-18. 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.
Daedalus / Pharos AI Factory (EuroHPC)
Lavrio, GR