Scrutica
Cloudflare, Inc.financials and operating footprint — geographic revenue split, segment mix, capex / FCF / buyback history, industry placement — sourced from licensed-database extracts and SEC EDGAR, joined to the supply-chain graph through the industry classification.
Where Cloudflare, Inc. sits in the compute supply chain: where its revenue comes from, what it spends capital on, and which counterparties move money in and out of the door.
No licensed-database enrichment loaded for this entity — geographic revenue, segments, capital allocation, and industry classification are absent. Coverage rules in the methodology.
Each hop carries its data source, source URL (where one exists), as-of date, and confidence label on the same line as the parent name. When two sources name different parents for the same hop, both sit on the page as alternates — the walker does not pick a winner.
Starting entity — the walker climbs from here, following documented parent / subsidiary edges in the ownership substrate.
Per Company disclosure (press / IR), as-of date not recorded (HIGHtier 1): Baselime is the documented parent.
Per Company disclosure (press / IR), as-of date not recorded (HIGHtier 1): Outerbase is the documented parent.
Per Company disclosure (press / IR), as-of date not recorded (HIGHtier 1): Replicate is the documented parent.
Per Company disclosure (press / IR), as-of date not recorded (HIGHtier 1): Partykit is the documented parent.
The walker hit a cycle at org-cloudflareand halted that branch. The cycle usually means one of three things: cross-holding, a JV that both sides claim control over, or stale data — a divestiture edge that should have been retired and wasn’t. The inbound edges on that entity are the place to look.
Annual $-flow and 3-month Pearson r per edge come from a licensed supply-chain database. Correlation is a coupling proxy — shared market sensitivity, not a causal channel. Sole-source edges are flagged inline.