Evidence over assertion

VERIDEX exists to make institutional investigations systematic and auditable: anchor a case to a real directory identity, gather what is genuinely available, keep the provenance of every fact, and let AI help without overreaching.

The problem

An authorized investigator who needs to understand one person has to gather fragments from many places: the internal directory, social accounts, phone and messaging signals, the public web, the institution’s own website. Then they have to make a judgment.

Done by hand, that work is slow, inconsistent and hard to audit. It is easy to treat a plausible match as proven, to lose track of where a fact came from, or to let an AI summary quietly become the conclusion.

VERIDEX makes gathering, provenance, review and analysis systematic, owned and auditable, and it refuses to turn correlation into identification.

Four principles

  • Identity is chosen, never matched

    A case starts from a person an investigator selects in the directory. Nothing is auto-selected, and the selection is a lead, not a conclusion.

  • Every fact keeps its origin

    Each item states where it came from, when, and what kind of thing it is, all the way into the final report.

  • A person decides

    Analysis reads only what an investigator has approved, and the decision is recorded.

  • AI within enforced limits

    The model helps inside boundaries the application sets. It cites its sources and never delivers a verdict.

Who it is for

Authorized investigators in a single institution that runs Microsoft Entra ID, working on cases their institution has authorized.

What VERIDEX is not

  • Not an identity-verification or background-check service. It never proves identity or ownership.
  • Not a mass-surveillance or arbitrary-profiling tool. Collection happens per case, per explicit action.
  • Not a compliance product. It makes no certification claims and records no legal basis today.
  • Not multi-tenant software. Each deployment serves one institution.

Direction

Themes we intend to work on. They are not commitments, and none of them is built today.

  • Planned

    Investigator authorization

    A role model so that only staff your institution authorizes can run investigations.

  • Planned

    Policies for shared resources

    Explicit access rules for the candidate pool and the institutional website index.

  • Planned

    Purpose and legal basis

    Recording why each investigation exists and on what basis.

  • Planned

    Team access

    Shared access to a case, and pagination for long case lists.

  • Planned

    Arabic website

    This site in Arabic, the third language the product’s reports already support.

See how an investigation flows

The five steps, from choosing a directory identity to exporting a report.

How it works