Entity graph
Model people, organizations, roles, skills, places, and anything else you match on, along with the relationships between them.
Graph-based matching software
Cupigraph models the people, organizations, and opportunities you work with as a graph of entities and relationships. When it suggests a match, it shows the paths that connect the two sides, so your team can see why they fit and make the call.
Role ↔ Person
3 paths · 1 open question
Controls Engineer and Candidate A-104. Select a path to highlight it.
Suggested for review. A person makes the decision.
Reviewer actions, shown for illustration: Shortlist or Pass.
How it works
Cupigraph does the tracing. Your team does the judging.
01 · Model
Bring in the records you already keep: profiles, roles, requests, organizations. Cupigraph turns them into entities and the relationships between them, and keeps the source of each one.
02 · Define
Choose which paths count, which are required, and how much each one weighs. Exclude any field that should never be used.
03 · Trace
For each pair, Cupigraph finds the paths that connect them under your criteria and notes any gaps or conflicts.
04 · Decide
Reviewers see the suggestion with its paths and open questions, then shortlist, pass, or ask for more. Nothing is decided automatically.
Platform
The pieces that turn records into suggestions your team can check, question, and act on.
Model people, organizations, roles, skills, places, and anything else you match on, along with the relationships between them.
Every suggestion lists the paths that connect both sides, in plain language a reviewer can check.
Choose which relationships count, which are required, and how much each one weighs. There are no hidden rules.
See what is missing or contradictory, not only what lines up, so open questions get asked early.
Each relationship carries its source, date, and consent scope. When consent is withdrawn, the edge stops being used.
Reviewers shortlist, pass, or annotate. Each decision is recorded with who made it and why.
Solutions
Wherever fit depends on how things relate, not on a single field, a graph explains it better.
Roles ↔ People
Match open roles with candidates, internal movers, or contractors, and show reviewers the skills, projects, and preferences that connect them.
Example path
Role —requires→ PLC programming ←practices— Candidate
Buyers ↔ Suppliers
Connect requests with suppliers or sellers through capabilities, specs, partners, and delivery coverage, including what a supplier can reach through its own partners.
Example path
Request —specifies→ Anodized finish ←provides— Partner ←subcontracts to— Supplier
Organizations ↔ Partners
Find partners, investors, or pilot customers whose focus overlaps with an organization's work, and see the shared programs, sectors, and portfolio links behind each suggestion.
Example path
Startup —member of→ Energy accelerator ←partners with— Fund
Mentors ↔ Mentees
Pair mentors with mentees, or learners with programs, through goals, experience, availability, and language, with the reasons for each pairing visible to the coordinator.
Example path
Mentee —wants to learn→ Product strategy ←has led— Mentor
What we hold to
01
Every suggestion comes with the paths that connect both sides, so anyone reviewing it can check the reasoning.
02
You decide which relationships count and how much. Cupigraph applies your definition of fit, not a hidden one.
03
Relationships record where they came from and what they may be used for. Nothing is used outside the scope it was shared for.
04
Cupigraph suggests and explains. A person reviews every match and makes the final call.
Tell us what you match and what a good fit means to you. We'll show you how it looks as a graph, with every path visible.