Skip to content
Cupigraph

About

A match should be able to explain itself.

Too much matching software returns a number and asks you to trust it. We started Cupigraph to make the reasoning visible: the actual connections between two sides, in a form people can check, question, and decide on.

The name

Two words, one idea.

Cupid is about matching. Graph is about precision. Together they describe what the product does.

  1. Matching

    Cupid

    Putting two sides in front of each other because they genuinely fit.

  2. Precision

    Graph

    Entities and the relationships between them: the structure that makes a fit precise and checkable.

  3. The product

    Cupigraph

    Matches that show their connection, the paths between two sides, ready for a person to review.

Why a graph

Because the reasons are in the connections.

01

Fit is relational

Two sides rarely fit because of one field. They fit because of how a skill, a place, a project, or a program links them. A graph keeps those links intact.

02

Evidence has a source

Every relationship in Cupigraph records where it came from. When a reviewer asks “says who?”, there is an answer.

03

Gaps are visible

A missing link is information too. Showing it means the right question gets asked before a decision, not after.

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.

What we don't build

Some things are easier to rule out at the start.

These are design constraints for the product, not features waiting on a roadmap.

  • Systems that accept or reject people automatically.
  • Scores that cannot say where they came from.
  • Criteria hidden from the people they affect.
  • Features that use data beyond the purpose it was shared for.

Where we are

Portland, Oregon, United States

contact@cupigraph.xyz

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.