One case. Every source. Provenance intact.
VERIDEX gives each investigator a private, owned workspace anchored to a single directory identity, and keeps everything attached to it, from raw evidence to the final report.
The case workspace
Every investigation has the same six sections, in the same order, so you always know where an item came from and what stage it has reached.
-
Overview
The case header, the subject, the state of each source and live activity.
-
Sources
Every collection path for this case, each started by an explicit action.
-
Evidence Review
Approve, reject or leave pending each collected item.
-
Analysis
Findings, synthesis and person analysis built from approved evidence.
-
AI Assistant
Questions about the case, answered with citations and caveats.
-
Reports
PDF reports rendered once from a fixed evidence snapshot.
Your sources, in one place
Six paths lead into a case. Each needs its own provider to be configured, and each runs only when an investigator asks it to.
-
Internal directory
Search, browse and open the exact person in Microsoft Entra ID. The anchor of every case.
Available -
Instagram
A selected candidate’s public profile, posts and comments, kept as a dated snapshot.
Needs a configured provider -
Phone and messaging
Public signals for one of the subject’s directory numbers, stored encrypted.
Needs a configured provider
Anchored to one directory identity
- Overview
- Sources
- Evidence Review
- Analysis
- AI Assistant
- Reports
-
Public web
A bounded search of the domains your deployment approves, with a short excerpt per page.
Needs a configured provider -
Institutional index
A local index of your institution’s own website, searched without a live provider call.
Needs a configured providerfor building the index -
Research agent
A model-driven research run that plans, searches and records leads within enforced limits.
Needs a configured providerdemo agent built in
Every external service sits behind one boundary
VERIDEX reaches each external service through a single adapter that checks what goes out and what comes back. Nothing a provider returns is treated as an instruction.
Opening a page never collects anything.
- Inputs validated against the case
- Allowlists, budgets and pacing enforced
- Web destinations checked by URL and DNS rules
- Disclosures to new destinations need your approval
- Responses validated and bounded
- Raw provider output never drives pages or the model as instructions
Directory, collection, search or AI provider your deployment has configured.
With its source and provenance attached. Sensitive values, such as phone numbers and raw provider output, are encrypted at rest.
Isolated and owned
Each case belongs to one investigator. Ownership is resolved on the server from the signed-in identity, never from anything the browser sends, and an investigator can hold at most one open case per person.
VERIDEX is a single-tenant application. Only members of your institution’s Microsoft Entra ID tenant can sign in. Signing in is not authorization to investigate: deciding who may run investigations, and why, remains your institution’s responsibility.
- Case for subject 1
- Case for subject 2
- Case for subject 3
Each case belongs to the identity that opened it, resolved on the server from the signed-in tenant and user. Asking for someone else’s case returns “not found”, never its contents.
Live, not refreshed
Collection and analysis can take minutes. They run in the background on a scheduler that shares capacity fairly between investigators, and the workspace updates in place as the server works. There is no “refresh this page”.
Completed analysis batches are reused when the same approved evidence is analysed again, so repeating a step does not repeat a provider call.
Investigation graph
A case-scoped view of directory facts as a graph of people, groups, devices and roles.
In development
Optional module: email campaigns
Separate from investigations. Where your institution enables it, campaigns move through review and approval before anything is sent, and only named operators can send.
See the capabilities in detail
Each feature, what it does today, and what it needs to run.