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. Every suggested match comes with 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

Role

Controls Engineer

Example Co. · Full-time

3 paths

Person

Candidate A-104

Open to relocating

?PLC programmingSkillROS 2ToolRobotics projectProjectSeattle areaPlacePacific NorthwestRegionWork authorizationRequirement

Why they connect

0 / 4
Your team decides

Example · fictional data

Relationships, not keywords

  • requires
  • practices
  • team uses
  • contributed to
  • based in
  • open to
  • offers
  • specifies
  • subcontracts to
  • ships to
  • invests at
  • member of
  • partners with
  • wants to learn
  • has led
  • speaks

How it works

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

Cupigraph does the tracing. Your team does the judging.

  1. 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. 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. 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. 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.

Example · fictional data

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

Required paths, weighted preferences, and excluded fields, all written down where reviewers can read them. There are no hidden rules.

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 ask for more. Each decision is recorded with who made it and why.

Gaps and conflicts

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

Example · fictional data

Solutions

Any two sides that should meet.

Wherever fit depends on how things relate, not on a single field, a graph explains it better.

  • Roles ↔ People

    Talent & hiring

    Match open roles with candidates, internal movers, or contractors, and show reviewers the skills, projects, and preferences that connect them.

    Example path

    Example · fictional data

    Role─requires→PLC programming←practices─Candidate

  • Buyers ↔ Suppliers

    Sourcing & marketplaces

    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

    Example · fictional data

    Request─specifies→Anodized finish←provides─Partner←subcontracts to─Supplier

  • Organizations ↔ Partners

    Partnerships & investment

    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

    Example · fictional data

    Startup─member of→Energy accelerator←partners with─Fund

  • Mentors ↔ Mentees

    Mentorship & programs

    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

    Example · fictional data

    Mentee─wants to learn→Product strategy←has led─Mentor

What we hold to

Four commitments behind every match.

They shape what the product does, and what it will never do.

  • 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 suggestion 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.