Follow the connection back to its evidence.
Hidden Ties investigates public material to map AI infrastructure relationships. We keep the claim, its source and its limits together so you can decide how to use the finding.
We research beyond provider announcements.
Company disclosures, engineering posts, technical documentation and public code can reveal relationships beyond a provider’s customer pages. Different sources establish different facts; we preserve those differences.
A finding describes a specific connection.
We identify the company, provider, product where recorded, role and workload where supported. A legal supplier list stays a declared supplier relationship. A technical reference stays a technical finding unless further evidence supports a broader claim.
You can see who said what, and when.
Each source shows its publisher, document type, publication date when stated and the date we observed it. Our summaries are editorial. A quotation appears only when the original passage has been captured and tied to the claim.
Unannounced is a scoped research finding.
Where we have reviewed provider customer pages, we can show a connection not found in those reviewed pages. The finding includes what was reviewed and when. It does not prove no announcement exists anywhere.
New research is not a new adoption.
Research updates describe newly published findings, added sources and corrections. The date we discover a connection is not necessarily the date the company began using the provider.
Unknown details stay unknown.
We do not fill missing workloads, spend, contract terms or provider roles with assumptions. A provider missing from an account’s documented connections is not proof the account has no supplier.
Corrections remain visible.
Report a claim or source that needs review. A resolved correction should preserve what changed, why it changed and the supporting evidence. Your saved research should identify affected connections rather than silently preserving a disputed claim.
Technical findings can be useful without being customer proof.
A company-owned repository may name a dependency. A developer guide may demonstrate a workflow. Both can help you choose what to investigate; neither automatically establishes a paid production customer.