Scrutica
Capacity, hardware inventory, ownership chain, and supply-chain position for Google Cedar Rapids. 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 Google Cedar Rapids, 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.
Alphabet, the documented owner of Google Cedar Rapids, sits as a seed node in 1 pre-built cascade scenario. Severity and decay are scenario parameters (editorial), not measured values: severity is the scenario's seed-impact value (per-node override where one is defined); decay reflects the curator's substitutability assessment for the disrupted role. Run any scenario to walk the propagation through the full supply-chain graph.
Restricted-jurisdiction customers retain some domestic cloud alternatives (Alibaba Cloud, Tencent Cloud, Yandex, regional sovereign clouds) but the GPU-density and frontier-model-availability gap with US hyperscalers is structural — partial substitution dampens propagation without closing it.
Description
Google's Cedar Rapids data center is similar to earlier Google data centers like New Albany and Omaha. Curiously, permitting suggests it will use more than twice as many cooling towers per building as those data centers, but most of the evidence suggests that the power capacity per building is largely unchanged.
Notes
Epoch estimation methods: our cooling equipment power model, regulatory filings, chip availability, chip efficiency, grid operator data.
Nearby Facilities (within 100 km)
source_url_contains_claim_verifiedChain terminates at a publicly-listed entity (Google). 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: Google
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.
Commitments dated 12+ years ago are framed in the past tense: closed-end private-market funds are typically structured on a ~10-year term plus extensions, and the source records the commitment event, not whether a position remains today.
GIC Private· 2006 commitment
GIC is associated with Singapore’s Singapore: National AI Strategy 2.0 / AISG / NSCC Sovereign Compute. See actor profile →
Committed capital in 2006 to a private-market fund whose documented portfolio included Google (chain hop 1). Commitment dollar value not disclosed (2006-08-08). The source records the commitment event, not whether a position remains.
The walk for Google Cedar Rapidsstarts 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.
Google Council Bluffs (East)
Council Bluffs, Iowa, US