A four-state force-directed relationship graph in plain SVG — a hand-written repulsion, spring and gravity simulation that converges and then stops, nodes you can drag and anchor, colour by group or by degree, and hover to light a node's neighbours and fade the rest.
Preview in your theme
Loading preview…
This component is part of Pro
The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.
status="ready" · 16 features across 4 product areas, joined by 23 undirected relationships worth 33,834 sessions. Two rows describe the same pair (Share links → Comments 1,510 and Comments → Share links 420) and fold into one edge of 1,930. Marker size = total sessions touching the feature; edge thickness = sessions. The run stops the moment its RMS node speed drops under 0.15px per tick — 158 ticks in a 512px card, 309 in a 990px one — and the count it needed is printed above the drawing.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
Ingest (4)
Analyse (5)
Collaborate (4)
Admin (3)
Marker size is the total sessions touching it. An edge's thickness is its weight. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 16 nodes joined by 23 relationships worth 33,834 sessions in total. Everything is reachable from everything else — one connected cluster. Busiest node Dashboards, with 6 partners and 10,534 sessions (31.1% of all weight). Strongest relationship Sources with Connectors: 3,900 sessions · 11.5% of all weight. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its group.
Node
Group
Marker
Partners
Weight
Share of all weight
Cluster
Dashboards
Analyse
square, solid
6
10,534 sessions
31.1%
1 of 1
Chart builder
Analyse
square, solid
4
7,620 sessions
22.5%
1 of 1
Roles
Admin
triangle, solid
4
2,730 sessions
8.1%
1 of 1
Sources
Ingest
circle, solid
4
7,230 sessions
21.4%
1 of 1
Alerts
Analyse
square, solid
3
3,720 sessions
11%
1 of 1
Metric catalog
Analyse
square, solid
3
6,090 sessions
18%
1 of 1
Share links
Collaborate
diamond, solid
3
4,950 sessions
14.6%
1 of 1
Sync schedule
Ingest
circle, solid
3
5,430 sessions
16%
1 of 1
Audit log
Admin
triangle, solid
2
1,000 sessions
3%
1 of 1
Comments
Collaborate
diamond, solid
2
2,450 sessions
7.2%
1 of 1
Connectors
Ingest
circle, solid
2
6,000 sessions
17.7%
1 of 1
CSV upload
Ingest
circle, solid
2
990 sessions
2.9%
1 of 1
Embeds
Collaborate
diamond, solid
2
804 sessions
2.4%
1 of 1
Slack digest
Collaborate
diamond, solid
2
2,210 sessions
6.5%
1 of 1
SQL editor
Analyse
square, solid
2
4,280 sessions
12.6%
1 of 1
SSO
Admin
triangle, solid
2
1,630 sessions
4.8%
1 of 1
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
Sources
Connectors
3,900 sessions
11.5%
Sources
Sync schedule
2,450 sessions
7.2%
Sources
CSV upload
640 sessions
1.9%
Sources
Roles
240 sessions
0.71%
Connectors
Sync schedule
2,100 sessions
6.2%
Sync schedule
Alerts
880 sessions
2.6%
CSV upload
Chart builder
350 sessions
1%
Dashboards
Chart builder
3,620 sessions
10.7%
Dashboards
Metric catalog
2,980 sessions
8.8%
Dashboards
Alerts
1,150 sessions
3.4%
Dashboards
Share links
2,260 sessions
6.7%
Dashboards
Embeds
44 sessions
0.13%
Dashboards
Roles
480 sessions
1.4%
SQL editor
Chart builder
2,410 sessions
7.1%
SQL editor
Metric catalog
1,870 sessions
5.5%
Chart builder
Metric catalog
1,240 sessions
3.7%
Alerts
Slack digest
1,690 sessions
5%
Comments
Share links
1,930 sessions
5.7%
Comments
Slack digest
520 sessions
1.5%
Share links
Embeds
760 sessions
2.2%
SSO
Roles
1,320 sessions
3.9%
SSO
Audit log
310 sessions
0.92%
Roles
Audit log
690 sessions
2%
onNodeSelect: nothing picked yet — click a node, or Tab in and press Enter
status="empty" · the contract is satisfied but not one entity is in the set — told apart from "still loading" and "the fetch failed".
Feature co-usage · last 30 days
Nothing connected yet
Entities and the relationships between them appear here once the first one is recorded.
status="loading" · a node-and-edge skeleton plus two placeholder lines, aria-hidden, no timer involved.
Feature co-usage · last 30 days
Loading network
status="error" · the fetch failed; Try again only appears when onRetry is passed, and clicking it swaps to ready.
Feature co-usage · last 30 days
Couldn't load this network
The data source didn't respond.
directed · a page graph where A → B and B → A are two different facts. Reciprocated pairs bow to opposite sides so neither hides under the other, one-way links stay straight, and Recipes links to itself — drawn as a loop, because a straight line between one point and itself has no length and renders as nothing at all.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
Getting started (2)
Guides (3)
Reference (3)
Support (1)
Marker size is the total clicks touching it. An edge's thickness is its weight. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 9 nodes joined by 14 directed edges worth 16,190 clicks in total. Everything is reachable from everything else — one connected cluster. Busiest node Quick start, with 3 partners and 7,960 clicks (49.2% of all weight). Strongest relationship Quick start to Installation: 4,200 clicks · 25.9% of all weight. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its group.
Node
Group
Marker
Partners
Weight
Share of all weight
Cluster
Quick start
Getting started
circle, solid
3
7,960 clicks
49.2%
1 of 1
API reference
Reference
diamond, solid
2
2,010 clicks
12.4%
1 of 1
CLI reference
Reference
diamond, solid
2
3,380 clicks
20.9%
1 of 1
Core concepts
Guides
square, solid
2
4,690 clicks
29%
1 of 1
Data contracts
Guides
square, solid
2
3,070 clicks
19%
1 of 1
Error codes
Reference
diamond, solid
2
1,570 clicks
9.7%
1 of 1
FAQ
Support
triangle, solid
2
800 clicks
4.9%
1 of 1
Installation
Getting started
circle, solid
2
6,900 clicks
42.6%
1 of 1
Recipes
Guides
square, solid
2
1,790 clicks
11.1%
1 of 1
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
Quick start
Installation
4,200 clicks
25.9%
Quick start
Core concepts
2,600 clicks
16.1%
Installation
Quick start
900 clicks
5.6%
Installation
CLI reference
1,800 clicks
11.1%
Core concepts
Data contracts
1,450 clicks
9%
Data contracts
Core concepts
640 clicks
4%
Data contracts
API reference
980 clicks
6.1%
Recipes
itself
210 clicks
1.3%
Recipes
CLI reference
380 clicks
2.3%
CLI reference
Recipes
1,200 clicks
7.4%
API reference
Error codes
720 clicks
4.4%
Error codes
API reference
310 clicks
1.9%
FAQ
Quick start
260 clicks
1.6%
FAQ
Error codes
540 clicks
3.3%
colorBy="degree" · the same features, coloured and sized by how many partners each one has rather than by product area. Tone runs chart-1 to chart-5, which is a monotone lightness ramp in both themes, and the radius follows the same number — so the ordering survives greyscale and colour-vision deficiency.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
2 partners (8)
3 partners (4)
4 partners (3)
5–6 partners (1)
Marker size is the number of partners, and so is its tone — two channels for one number. An edge's thickness is its weight. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 16 nodes joined by 23 relationships worth 33,834 sessions in total. Everything is reachable from everything else — one connected cluster. Busiest node Dashboards, with 6 partners and 10,534 sessions (31.1% of all weight). Strongest relationship Sources with Connectors: 3,900 sessions · 11.5% of all weight. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its degree bucket.
Node
Degree bucket
Marker
Partners
Weight
Share of all weight
Cluster
Dashboards
5–6
hexagon, solid
6
10,534 sessions
31.1%
1 of 1
Chart builder
4
triangle, solid
4
7,620 sessions
22.5%
1 of 1
Roles
4
triangle, solid
4
2,730 sessions
8.1%
1 of 1
Sources
4
triangle, solid
4
7,230 sessions
21.4%
1 of 1
Alerts
3
diamond, solid
3
3,720 sessions
11%
1 of 1
Metric catalog
3
diamond, solid
3
6,090 sessions
18%
1 of 1
Share links
3
diamond, solid
3
4,950 sessions
14.6%
1 of 1
Sync schedule
3
diamond, solid
3
5,430 sessions
16%
1 of 1
Audit log
2
square, solid
2
1,000 sessions
3%
1 of 1
Comments
2
square, solid
2
2,450 sessions
7.2%
1 of 1
Connectors
2
square, solid
2
6,000 sessions
17.7%
1 of 1
CSV upload
2
square, solid
2
990 sessions
2.9%
1 of 1
Embeds
2
square, solid
2
804 sessions
2.4%
1 of 1
Slack digest
2
square, solid
2
2,210 sessions
6.5%
1 of 1
SQL editor
2
square, solid
2
4,280 sessions
12.6%
1 of 1
SSO
2
square, solid
2
1,630 sessions
4.8%
1 of 1
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
Sources
Connectors
3,900 sessions
11.5%
Sources
Sync schedule
2,450 sessions
7.2%
Sources
CSV upload
640 sessions
1.9%
Sources
Roles
240 sessions
0.71%
Connectors
Sync schedule
2,100 sessions
6.2%
Sync schedule
Alerts
880 sessions
2.6%
CSV upload
Chart builder
350 sessions
1%
Dashboards
Chart builder
3,620 sessions
10.7%
Dashboards
Metric catalog
2,980 sessions
8.8%
Dashboards
Alerts
1,150 sessions
3.4%
Dashboards
Share links
2,260 sessions
6.7%
Dashboards
Embeds
44 sessions
0.13%
Dashboards
Roles
480 sessions
1.4%
SQL editor
Chart builder
2,410 sessions
7.1%
SQL editor
Metric catalog
1,870 sessions
5.5%
Chart builder
Metric catalog
1,240 sessions
3.7%
Alerts
Slack digest
1,690 sessions
5%
Comments
Share links
1,930 sessions
5.7%
Comments
Slack digest
520 sessions
1.5%
Share links
Embeds
760 sessions
2.2%
SSO
Roles
1,320 sessions
3.9%
SSO
Audit log
310 sessions
0.92%
Roles
Audit log
690 sessions
2%
four clusters, one of them a castaway · nothing joins the money cluster to the identity cluster or either to the reporting pair, and Legacy exporter talks to nobody at all: it is drawn hollow and dashed rather than dropped, and both facts are stated in the summary. This is the reading a fixed layout cannot give you.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
Money (4)
Identity (3)
Reporting (3)
Marker size is the total calls touching it. An edge's thickness is its weight. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 10 nodes joined by 8 relationships worth 4,250 calls in total. They fall into 4 separate clusters, with nothing linking one to the next. Busiest node Token service, with 2 partners and 1,600 calls (37.6% of all weight). Strongest relationship Login with Token service: 900 calls · 21.2% of all weight. 1 node has no relationship at all: Legacy exporter. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its group.
Node
Group
Marker
Partners
Weight
Share of all weight
Cluster
Ledger
Money
circle, solid
3
1,310 calls
30.8%
1 of 4
Checkout
Money
circle, solid
2
1,080 calls
25.4%
1 of 4
Login
Identity
square, solid
2
1,080 calls
25.4%
2 of 4
Payments
Money
circle, solid
2
1,460 calls
34.4%
1 of 4
Sessions
Identity
square, solid
2
880 calls
20.7%
2 of 4
Token service
Identity
square, solid
2
1,600 calls
37.6%
2 of 4
Reconciler
Money
circle, solid
1
410 calls
9.6%
1 of 4
Report runner
Reporting
diamond, solid
1
340 calls
8%
3 of 4
Warehouse
Reporting
diamond, solid
1
340 calls
8%
3 of 4
Legacy exporter
Reporting
diamond, solid
0
0 calls
0%
4 of 4
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
Checkout
Payments
820 calls
19.3%
Checkout
Ledger
260 calls
6.1%
Payments
Ledger
640 calls
15.1%
Ledger
Reconciler
410 calls
9.6%
Login
Token service
900 calls
21.2%
Login
Sessions
180 calls
4.2%
Token service
Sessions
700 calls
16.5%
Warehouse
Report runner
340 calls
8%
animate={false} · the identical payload settled in one synchronous pass instead of over animation frames. It is the same ticks in the same order, so the layout matches the card above exactly — and it is what every reader with prefers-reduced-motion gets, automatically.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
Money (4)
Identity (3)
Reporting (3)
Marker size is the total calls touching it. An edge's thickness is its weight. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 10 nodes joined by 8 relationships worth 4,250 calls in total. They fall into 4 separate clusters, with nothing linking one to the next. Busiest node Token service, with 2 partners and 1,600 calls (37.6% of all weight). Strongest relationship Login with Token service: 900 calls · 21.2% of all weight. 1 node has no relationship at all: Legacy exporter. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its group.
Node
Group
Marker
Partners
Weight
Share of all weight
Cluster
Ledger
Money
circle, solid
3
1,310 calls
30.8%
1 of 4
Checkout
Money
circle, solid
2
1,080 calls
25.4%
1 of 4
Login
Identity
square, solid
2
1,080 calls
25.4%
2 of 4
Payments
Money
circle, solid
2
1,460 calls
34.4%
1 of 4
Sessions
Identity
square, solid
2
880 calls
20.7%
2 of 4
Token service
Identity
square, solid
2
1,600 calls
37.6%
2 of 4
Reconciler
Money
circle, solid
1
410 calls
9.6%
1 of 4
Report runner
Reporting
diamond, solid
1
340 calls
8%
3 of 4
Warehouse
Reporting
diamond, solid
1
340 calls
8%
3 of 4
Legacy exporter
Reporting
diamond, solid
0
0 calls
0%
4 of 4
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
Checkout
Payments
820 calls
19.3%
Checkout
Ledger
260 calls
6.1%
Payments
Ledger
640 calls
15.1%
Ledger
Reconciler
410 calls
9.6%
Login
Token service
900 calls
21.2%
Login
Sessions
180 calls
4.2%
Token service
Sessions
700 calls
16.5%
Warehouse
Report runner
340 calls
8%
degenerate data · one row: a single entity with no relationships at all. It still gets a marker, the summary says there are no relationships instead of naming a strongest edge that does not exist, and the run settles in a handful of ticks.
Cold start · single entity
1 node · 0 relationships · settling · tick 0
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
0 partners (1)
Marker size is the number of partners, and so is its tone — two channels for one number. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 1 node with no relationships between them at all. 1 node has no relationship at all: Core service. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its degree bucket.
Node
Degree bucket
Marker
Partners
Weight
Share of all weight
Cluster
Core service
0
circle, solid
0
0 calls
0%
1 of 1
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
degenerate data · one relationship at 100%: two nodes and a single edge of 1,200. It is both the thickest and the thinnest — thickness encodes nothing here, so it draws at a neutral width rather than a maxed-out 6px pretending to be as strong as strong gets.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
Client (1)
Server (1)
Marker size is the total messages touching it. Every relationship weighs the same, so thickness is carrying nothing and every edge is drawn at one neutral width. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 2 nodes joined by 1 relationship worth 1,200 messages in total. Everything is reachable from everything else — one connected cluster. Busiest node Mobile client, with 1 partner and 1,200 messages (100% of all weight). Every relationship weighs the same 1,200 messages, so thickness encodes nothing here and all 1 edge is drawn at one neutral width. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its group.
Node
Group
Marker
Partners
Weight
Share of all weight
Cluster
Message broker
Server
square, solid
1
1,200 messages
100%
1 of 1
Mobile client
Client
circle, solid
1
1,200 messages
100%
1 of 1
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
Mobile client
Message broker
1,200 messages
100%
degenerate data · no weights at all: ten rows written without a value, so every edge reads as 1. Nothing is thicker than anything else, every edge takes the neutral width, and the summary says outright that they all weigh the same.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
1 partners (1)
2 partners (3)
3 partners (3)
4 partners (1)
Marker size is the number of partners, and so is its tone — two channels for one number. Every relationship weighs the same, so thickness is carrying nothing and every edge is drawn at one neutral width. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears.
Force-directed network: 8 nodes joined by 10 relationships worth 10 tickets in total. Everything is reachable from everything else — one connected cluster. Busiest node login, with 4 partners and 4 tickets (40% of all weight). Every relationship weighs the same 1 tickets, so thickness encodes nothing here and all 10 edges are drawn at one neutral width. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its degree bucket.
Node
Degree bucket
Marker
Partners
Weight
Share of all weight
Cluster
login
4
hexagon, solid
4
4 tickets
40%
1 of 1
billing
3
triangle, solid
3
3 tickets
30%
1 of 1
invoice
3
triangle, solid
3
3 tickets
30%
1 of 1
mfa
3
triangle, solid
3
3 tickets
30%
1 of 1
recovery
2
diamond, solid
2
2 tickets
20%
1 of 1
refund
2
diamond, solid
2
2 tickets
20%
1 of 1
sso
2
diamond, solid
2
2 tickets
20%
1 of 1
tax
1
square, solid
1
1 tickets
10%
1 of 1
Every relationship, with the weight it carries and its share of all the weight in the network.
From
To
Weight
Share
billing
refund
1 tickets
10%
billing
invoice
1 tickets
10%
billing
login
1 tickets
10%
refund
invoice
1 tickets
10%
invoice
tax
1 tickets
10%
login
sso
1 tickets
10%
login
mfa
1 tickets
10%
login
recovery
1 tickets
10%
sso
mfa
1 tickets
10%
mfa
recovery
1 tickets
10%
stress data · 65 rows for 64 drawn nodes across 11 groups: the palette holds 5 colours and 5 shapes, so groups 6–10 repeat both and are told apart by a dashed stroke while group 11 switches to dotted. Company names run past the 16-character budget and are truncated with the full name kept in the tooltip and the table. One node is never called and draws hollow; one row points at an id that is not in the set, one carries zero weight and one repeats an existing node id — all three are dropped and named at the top of the card. Only 24 labels are drawn at rest and the card says how many are held back; the hairball warning is printed rather than enforced, because every node is still drawn. This many nodes need 714 ticks to settle in a 512px card and 944 in a 990px one, so the budget is raised from the default 500 — at which the card would stop early and say so rather than pretend — and six ticks are taken per frame to keep the settle under four seconds.
1 edge points at a node that is not in the set · 1 zero-weight edge · 1 duplicate node id — ignored.
Point at a node or an edge — or press Tab and use the arrow keys — to read its numbers.
Ingress (6)
Identity (6)
Catalogue (6)
Checkout (6)
Payments (6)
Fulfilment (6)
Insight (6)
Archive (6)
Partners (6)
Growth (5)
Platform (5)
Marker size is the total calls touching it. An edge's thickness is its weight. Distance is not data: the layout is produced by a force simulation, so how far apart two nodes end up says nothing beyond which of them are joined. Drag a node to pull it out of the pile — it stays where you drop it until you release it. Arrow keys walk the nodes, ↓ steps into one's edges, Enter picks, Shift and an arrow move the focused node, Backspace releases it, Escape clears. 24 of 64 labels are drawn at rest, busiest first; the other 40 appear on hover and focus and are all listed in the table below. 30 labels are shortened; the table names every node in full. At 64 nodes this is past the point where a force layout reads as a shape rather than a hairball — every node is still drawn, but aggregating the tail upstream will tell the story better.
Force-directed network: 64 nodes joined by 99 relationships worth 49,156 calls in total. They fall into 4 separate clusters, with nothing linking one to the next. Busiest node Hessel - Fahey, with 9 partners and 5,798 calls (11.8% of all weight). Strongest relationship Ratke, Wolf-Grimes and Kuvalis with Hahn - Weimann: 895 calls · 1.8% of all weight. 3 nodes have no relationship at all: Nader Group, Turner and Sons, Brakus LLC. Positions come from a force simulation and carry no meaning of their own: how far apart two nodes sit is not a measurement, only which of them are joined and how heavily.
Every node, busiest first, with the weight touching it and the marker that stands for its group.
Node
Group
Marker
Partners
Weight
Share of all weight
Cluster
Hessel - Fahey
Ingress
circle, solid
9
5,798 calls
11.8%
1 of 4
Schultz - Nicolas
Payments
hexagon, solid
7
4,421 calls
9%
1 of 4
Bruen - Dickinson
Archive
diamond, dashed
6
2,023 calls
4.1%
1 of 4
Pollich, Lang and Glover
Payments
hexagon, solid
6
1,790 calls
3.6%
1 of 4
Daugherty, Torp and Hand
Catalogue
diamond, solid
5
3,367 calls
6.8%
1 of 4
Hahn - Weimann
Insight
square, dashed
5
3,403 calls
6.9%
1 of 4
Murazik and Sons
Catalogue
diamond, solid
5
2,164 calls
4.4%
1 of 4
Robel, Boyle and Ankunding
Archive
diamond, dashed
5
2,765 calls
5.6%
1 of 4
Roob - Wunsch
Platform
circle, dotted
5
2,696 calls
5.5%
1 of 4
Walker, Nikolaus and Konopelski
Catalogue
diamond, solid
5
1,952 calls
4%
1 of 4
Abbott, Kunze and Rowe
Ingress
circle, solid
4
1,357 calls
2.8%
1 of 4
Armstrong Group
Growth
hexagon, dashed
4
1,203 calls
2.4%
1 of 4
Aufderhar, Huels and Koepp
Fulfilment
circle, dashed
4
1,719 calls
3.5%
1 of 4
Considine Inc
Fulfilment
circle, dashed
4
2,141 calls
4.4%
1 of 4
Cruickshank Group
Identity
square, solid
4
1,519 calls
3.1%
1 of 4
Ebert, Hahn and Shanahan
Checkout
triangle, solid
4
1,402 calls
2.9%
1 of 4
Hilll Inc
Checkout
triangle, solid
4
2,175 calls
4.4%
1 of 4
Ratke, Wolf-Grimes and Kuvalis
Identity
square, solid
4
2,178 calls
4.4%
1 of 4
Smitham Group
Archive
diamond, dashed
4
2,008 calls
4.1%
1 of 4
Steuber, Kerluke and Halvorson
Partners
triangle, dashed
4
2,330 calls
4.7%
1 of 4
Weimann, Kuhic and Hermann
Payments
hexagon, solid
4
1,408 calls
2.9%
1 of 4
Baumbach - Yost
Catalogue
diamond, solid
3
1,107 calls
2.3%
1 of 4
Bosco Group
Identity
square, solid
3
1,051 calls
2.1%
1 of 4
DuBuque Group
Checkout
triangle, solid
3
1,328 calls
2.7%
1 of 4
Hahn - Erdman
Partners
triangle, dashed
3
1,639 calls
3.3%
1 of 4
Heaney - Ortiz
Identity
square, solid
3
1,174 calls
2.4%
1 of 4
Heathcote, Rohan and Mann
Checkout
triangle, solid
3
702 calls
1.4%
1 of 4
Jaskolski and Sons
Checkout
triangle, solid
3
1,336 calls
2.7%
1 of 4
Klocko Inc
Insight
square, dashed
3
1,279 calls
2.6%
1 of 4
Kohler - Hane
Partners
triangle, dashed
3
1,939 calls
3.9%
1 of 4
Leannon Inc
Partners
triangle, dashed
3
1,934 calls
3.9%
1 of 4
Lesch LLC
Fulfilment
circle, dashed
3
1,492 calls
3%
1 of 4
Lueilwitz and Sons
Platform
circle, dotted
3
1,593 calls
3.2%
1 of 4
Metz Inc
Ingress
circle, solid
3
2,110 calls
4.3%
1 of 4
Morar Inc
Insight
square, dashed
3
2,414 calls
4.9%
1 of 4
Nolan-Effertz - Walsh
Growth
hexagon, dashed
3
1,964 calls
4%
1 of 4
Orn, Bauch and DuBuque
Insight
square, dashed
3
1,830 calls
3.7%
1 of 4
Osinski - Von
Platform
circle, dotted
3
1,742 calls
3.5%
1 of 4
Steuber - Swift
Catalogue
diamond, solid
3
856 calls
1.7%
1 of 4
Tremblay, Wolff and Marks
Partners
triangle, dashed
3
1,300 calls
2.6%
1 of 4
Weber - Okuneva
Fulfilment
circle, dashed
3
1,028 calls
2.1%
1 of 4
Weber, Reilly and Miller-Dach
Payments
hexagon, solid
3
1,790 calls
3.6%
1 of 4
Willms - Welch
Insight
square, dashed
3
2,040 calls
4.2%
1 of 4
Bins - Schinner
Identity
square, solid
2
1,202 calls
2.4%
1 of 4
Braun-Bradtke LLC
Growth
hexagon, dashed
2
753 calls
1.5%
1 of 4
Dickens - Keebler
Growth
hexagon, dashed
2
942 calls
1.9%
1 of 4
Haley, Schuster-Stanton and Kuhlman
Catalogue
diamond, solid
2
930 calls
1.9%
1 of 4
Kassulke and Sons
Growth
hexagon, dashed
2
227 calls
0.46%
1 of 4
Kuvalis - Gulgowski
Ingress
circle, solid
2
1,560 calls
3.2%
1 of 4
Labadie and Sons
Ingress
circle, solid
2
725 calls
1.5%
1 of 4
Lang - Labadie
Payments
hexagon, solid
2
1,164 calls
2.4%
1 of 4
Swaniawski Inc
Archive
diamond, dashed
2
1,073 calls
2.2%
1 of 4
Walker Inc
Platform
circle, dotted
2
1,237 calls
2.5%
1 of 4
Grant and Sons
Fulfilment
circle, dashed
1
489 calls
0.99%
1 of 4
Kuhlman - Gislason
Archive
diamond, dashed
1
221 calls
0.45%
1 of 4
Lesch, Terry and Kulas
Checkout
triangle, solid
1
725 calls
1.5%
1 of 4
Lynch - Wehner
Partners
triangle, dashed
1
210 calls
0.43%
1 of 4
Rogahn - Baumbach
Payments
hexagon, solid
1
574 calls
1.2%
1 of 4
Senger, Hodkiewicz and Stehr-Bauch
Identity
square, solid
1
682 calls
1.4%
1 of 4
Stehr - Kemmer
Platform
circle, dotted
1
873 calls
1.8%
1 of 4
Wiegand, Schowalter and Cole
Ingress
circle, solid
1
354 calls
0.72%
1 of 4
Brakus LLC
Archive
diamond, dashed
0
0 calls
0%
4 of 4
Nader Group
Fulfilment
circle, dashed
0
0 calls
0%
2 of 4
Turner and Sons
Insight
square, dashed
0
0 calls
0%
3 of 4
Every relationship, with the weight it carries and its share of all the weight in the network.
Zyeon UI