Scrutica
Where OVHcloud sits in the compute supply chain — geographic revenue split, segment mix, capex / FCF / buyback history, and industry placement — sourced from licensed-database extracts and SEC EDGAR, joined to the supply-chain graph through the industry classification.
Dollar flows are annual figures from the fiscal year labelled on the row — SEC segment and >10%-customer disclosures, re-derived company disclosures, or a licensed supply-chain database; per-row source and authority tier on hover. A row without a year means the source does not state the period. Disclosures older than 5 years are tagged historical and ordered below current rows — they are kept as evidence of what was disclosed then, not as evidence of a present relationship, and the counterparty may since have been acquired or dissolved. The 3-month Pearson r comes from a licensed supply-chain database; correlation is a coupling proxy — shared market sensitivity, not a causal channel. Sole-source edges are flagged inline.
The substrates above join to the platform's analytical surfaces. Each link carries OVHcloud's own numbers into the tool that acts on them.
2 upstream · 1 downstream — the interactive graph opens with OVHcloud selected. The cascade simulator propagates seed disruptions across this same edge set, weighted by the curator's substitutability assessment.
The facility table filtered to exactly these records — class, status, and power per row, exportable with full provenance columns.
Licensed sources do reach OVHcloud: the supply relationships above are drawn from a licensed supply-chain database. What is missing is one specific feed — the corporate-financials extract behind this profile (geographic revenue, segment mix, capital allocation), which covers a loaded set of listed companies that OVHcloud is not among; the gap is in coverage, not in the record. The public industry classification (SIC, NAICS) is absent as well. Coverage rules in the methodology.