Pilot
Run a read-only pilot with us.
We are working with a small number of design partners: companies with more than one identity provider, and an auditor or regulator who asks about leavers and privileged access.
What a pilot looks like
- 30 to 60 days, read-only throughout
- Okta and Microsoft Entra ID, plus your HR worker export
- Your governance tool, if you have one
- Two or three applications you choose
- A dedicated hosted instance, or inside your own environment
Time from your team
- Week one, about half a day: a security review, creating the read-only credentials, and setting up the HR export
- Then about an hour a week from your IAM lead to review findings
- A few hours from an expert to write and judge 40 test questions
How it runs
A fixed sequence, so you always know what's next.
Before day one
Security review and scope
We share the architecture, data flow and connector permissions. You choose the systems, deadlines and the people who judge results.
Week 1
Connect read-only
Your team creates read-only credentials. We run the first sync and show you one record per person, with the reconciliation counts.
Week 2
First findings and test set
Clocks and findings on your data. Your expert writes 40 test questions and expected answers.
Weeks 3 to 7
Use it in real work, and test side by side
A weekly review of what it found and what was wrong. We run the side-by-side cases against the tools you already own.
Final week
Readout and deletion
Results against every measure, an audit pack, and deletion of your instance and data.
How we judge it, together
Agreed before we start. If it doesn't meet them, you'll hear it from us first.
| Measure | Target |
|---|---|
| Accuracy | At least 90% correct or properly qualified on 40 cases your expert writes, reported as answered and declined separately |
| Evidence | Every finding links to its source records, and the evidence chain verifies |
| Time to triage | At least 50% faster than your current workflow |
| Isolation | No data from any other company, tested |
| Side by side | Results of the three comparison cases, published as they are |
Questions we hear
Can it change anything in our systems?
No. Connectors use read-only permissions, and there is no code that writes to your identity systems. Remediation stays with your team and your existing tools.
Where does our data live during the pilot?
Either in a dedicated instance and database for your company only, or inside your own environment. You choose before anything is connected.
We already have a governance tool. Why this?
Governance knows what was approved, and identity providers know what exists. VerifAIdentity checks them against each other and against HR, including systems governance doesn't connect to, and keeps deadline-based evidence for auditors. The side-by-side cases test whether that adds anything for you.
Is it production ready?
Not yet. It is built and tested on lab data in our own tenants. A pilot is how we measure it on real data, with targets agreed up front.
What happens to our data at the end?
The instance and its data are deleted, and we confirm it in writing. You keep the readout and the audit pack.
Tell us about your identity setup.
Which identity providers you run, your governance tool, and what your auditors ask about. We'll reply with a proposed scope.