Blind to relationships
A clean name connected to a designated party still clears.
Platform · Network analysis
Connections Graph, the network behind the name
See how a customer connects to accounts, companies and known risk, so a clean name with a dirty neighbourhood does not clear on its own.
6 hops
Path depth searched
Real-time
Path detection
UBO
Ownership resolved
1 view
Accounts, entities and lists
Why this matters
Risk hides one relationship away
A customer can pass every direct check and still sit two hops from a sanctioned entity through a shared director or a beneficial owner. Single-name screening never sees it. Complead resolves the network around a customer and traces the path to known risk before you clear the name.
Manual tracing
Analysts rebuild ownership by hand across registries and spreadsheets.
Hidden UBOs
The person who actually controls the account is three companies deep.
How it works
Scroll to advance
Four steps, from a name to its network
-
Step 01
Resolve the entity
Records for the same real-world entity are merged across your systems and external data.
-
Step 02
Build the graph
Accounts, directors, owners and counterparties become nodes and edges around the entity.
-
Step 03
Trace paths to risk
The graph is searched for paths to sanctioned, PEP or adverse-media entities, up to six hops.
-
Step 04
Attach to the case
The path and the network become evidence in the case, with every hop sourced.
complead / resolve
- Delta CorpLtd
- records merged3
- canonical entity1
complead / build
- nodes14
- edges22
- shared directors2
- linked accounts4
complead / trace
- Pathfound
- Delta Corp → owner → OFACSDN
- hops3
complead / attach
- Added to case#7719
- path 3hops
- each edgesourced
Resolve
Build
Trace
Attach
Capabilities
What the product actually does
Entity resolution
Records for one real-world entity merged across sources.
Ownership resolution
UBO and control chains traced through company layers.
Path detection
Automatic paths from a customer to known risk, up to six hops.
Shared attribute links
Common directors, addresses and accounts surfaced as edges.
Sourced edges
Every relationship shows where it came from.
Case export
The network and the path exported as evidence.
Product tour
Three screens your team lives in
The network, laid out
Every account, entity and owner around a customer, with risk nodes highlighted.
- Nodes by type and risk
- Zoom from entity to full network
- Highlight paths to designated parties
complead / graph
- Delta Corpcenter
- nodes14
- sanctioned UBO 3 hops1
The shortest route to risk
Ranked paths from the customer to any known-risk entity, each hop sourced.
- Ranked by hop count and risk
- Each edge with its source
- One click to add to a case
complead / paths
- Path1
- hops3
- OFACSDN
- via owner. Path2
- hops5
- PEP
Who actually controls the account
The UBO chain resolved through layers, with percentages where available.
- Control chain by percentage
- Layers collapsed or expanded
- Missing links flagged
complead / ownership
- Delta Corp → HoldCo 80% → Individual100%
- UBOresolved
What is connected
What the graph draws on, and how current it is
The graph combines your customer data with corporate registries, screening lists and adverse media, refreshed on the platform schedule.
Data sources
Your data
Accounts, customers, counterparties
Registries
Company ownership and directorship data
Risk lists
Sanctions, PEP and watchlist entities as nodes
Freshness
Risk nodes refreshed every 15 minutes
Runs on Fusion
The network is an input to the Fusion score
A path to a designated entity raises the customer risk score, so relationship risk is priced into the same number as sanctions and behaviour, not tracked on the side.
This product
Connections Graph
Entity resolution, paths, ownership
Feeds into
Fusion engine
Network proximity as a scoring input
You get
One risk score
Aware of who the customer is connected to
Integration
Push an entity, query its network
Send customer and counterparty data, then query the resolved network and its paths to risk.
// query paths to known risk
POST /v1/graph/paths "entity_id": "delta_corp", "target": "sanctioned", "max_hops": 6
200 OK · 1 path · 3 hops · OFAC SDN
// push a counterparty relationship
POST /v1/graph/edges "from": "cust_8841", "to": "delta_corp", "type": "counterparty"
201 Created
FAQ
Before you ask us
How deep does path detection go?
Up to six hops by default, configurable, so an indirect link to a designated party is still found.
Where does ownership data come from?
Corporate registries combined with your own data, resolved into a single control chain.
Is every relationship sourced?
Yes. Each edge shows where it came from, so a path stands up as evidence.
Can we feed our own counterparty data?
Yes, over the API, alongside registry and risk-list data.
How current are the risk nodes?
Sanctions, PEP and watchlist nodes refresh every 15 minutes.
Where is our data stored?
You choose the region: EU, UK or Türkiye.
Testimonials
All case studies
What compliance teams say
Complead provides ultimate control via its case management and safelist systems. Automated API operations significantly reduced my team's manual workload.
Using the API we run AML controls automatically and stay compliant, while reducing our team's daily workload.
With Complead we offer fast, easy, secure onboarding. We focus on real risks, not false positives.
See the network behind your own names
Bring a sample of entities. In 30 minutes you will see the graph, the paths to risk and the evidence they produce.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data