VerifAIdentity

About

Built from the questions auditors ask every quarter.

VerifAIdentity started from a simple, recurring question that no single identity tool answers on its own: is every person where they should be, in every system?

Why we're building it

Most companies run more than one identity provider, a governance tool, and an HR system. Each is right about itself. The gaps sit between them: the contractor whose access outlived the contract, the admin role nobody approved, the account in a system governance never connected to.

Proving those gaps are closed usually means exports, spreadsheets and a week before every audit. We think it should be continuous, evidence-backed, and honest about what it can't see.

How we work

Evidence over claims

Every finding points to its source records. So does this website: examples come from our lab, labelled as such, and every number has a method.

Say what we can't see

A gap in the data is reported as a gap. We'd rather show "cannot be verified" than a pass we can't prove.

Read-only, by design

A tool that checks access shouldn't need write access. We never ask for it.

Where we are now

The product is built and tested on a simulated company in our own Okta, Microsoft Entra ID, PingOne and midPoint tenants. We are looking for a few design partners to measure it on real data.

VerifAIdentity is a working name. The company is founder-led and self-funded. Get in touch if you'd like to help shape it.

See it on your own identity data.

A read-only pilot with Okta, Microsoft Entra ID and your HR export. 30 to 60 days, measured against targets we agree up front.