Skip to content
Cupigraph

Graph-based matching software

Show the connection, not just the score.

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.

  • Paths, not just scores
  • Criteria you define
  • People make the call
cupigraph · match review
Example · fictional data

Role ↔ Person

?PLC programmingSkillROS 2ToolRobotics projectProjectSeattle areaPlacePacific NorthwestRegionWork authorizationRequirementRoleControls EngineerPersonCandidate A-104

Why they connect

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

From your records to a decision a person can stand behind.

Cupigraph does the tracing. Your team does the judging.

  1. 01 · Model

    Map your entities and relationships

    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.

  2. 02 · Define

    Say what a good fit means

    Choose which paths count, which are required, and how much each one weighs. Exclude any field that should never be used.

  3. 03 · Trace

    See the paths between two sides

    For each pair, Cupigraph finds the paths that connect them under your criteria and notes any gaps or conflicts.

  4. 04 · Decide

    A person makes the call

    Reviewers see the suggestion with its paths and open questions, then shortlist, pass, or ask for more. Nothing is decided automatically.

Platform

One graph, every reason in view.

The pieces that turn records into suggestions your team can check, question, and act on.

Entity graph

Model people, organizations, roles, skills, places, and anything else you match on, along with the relationships between them.

Path explanations

Every suggestion lists the paths that connect both sides, in plain language a reviewer can check.

Criteria you define

Choose which relationships count, which are required, and how much each one weighs. There are no hidden rules.

Gaps and conflicts

See what is missing or contradictory, not only what lines up, so open questions get asked early.

Consent on every edge

Each relationship carries its source, date, and consent scope. When consent is withdrawn, the edge stops being used.

Review workflow

Reviewers shortlist, pass, or annotate. Each decision is recorded with who made it and why.

What we hold to

Four commitments behind every match.

  • 01

    Explainable matches

    Every suggestion comes with the paths that connect both sides, so anyone reviewing it can check the reasoning.

  • 02

    Your criteria, not ours

    You decide which relationships count and how much. Cupigraph applies your definition of fit, not a hidden one.

  • 03

    Privacy and consent

    Relationships record where they came from and what they may be used for. Nothing is used outside the scope it was shared for.

  • 04

    People decide

    Cupigraph suggests and explains. A person reviews every match and makes the final call.

Bring us two sides that should meet.

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.