Why IdentityFirst?
Because buyers need an evidence-first answer, not more noise: what is public now, what starts with MRI, and what remains qualified or private beta.
Why an evidence-first layer, not just another point tool
Identity issues usually overlap. IdentityFirst keeps the evidence, findings, and next steps consistent instead of asking teams to rebuild the story from separate tools.
Separate tools create separate stories
If the answer lives in five places, it takes longer to explain and harder to trust.
One connection, more use
Connect once and reuse the same evidence for assessment, review, and follow-up.
Consistent view of access
The aim is a single view of who has access, where it came from, and why it matters.
Clear evidence trail
You can show what was found, what was done, and what is still open without rebuilding the story later.
What is live and what is not
We keep the public story clear about what is available now, what is controlled rollout, and what remains private beta.
- MRI public GA: read-only start, plain-English findings, and clear next steps
- Core controlled rollout: recurring review, drift awareness, and better prioritisation for approved deployments
- Enhanced private beta: guided analysis and operator support for approved later-stage pilots
- AISF private beta: governed, human-approved action workflows where written scope and approvals exist
- Higher-tier write paths are qualified, not part of the default MRI promise
- Connector and workflow breadth depends on product tier, maturity, and written scope
We are not the right fit if…
Clear fit matters more than trying to be everything to everyone.
You need fully mature connectors today
If you need everything to behave like a long-established platform on day one, we are not the right fit yet.
You want a direct IGA replacement
IdentityFirst is there to improve visibility and action around identity risk, not replace every IGA function.
No one can act on the findings
You still need someone who can review the output and move the work forward.
You need on-premises deployment
If an on-prem requirement is non-negotiable, this is not the right route today.
Our commitments
- MRI starts read-only, and higher-tier write paths require explicit human approval
- We say clearly what is live, what is beta, and what is still coming
- We are UK-based and built for regulated environments
- We keep the output exportable and easy to carry into internal reviews
See MRI in context
Book a demo and we will show what the public MRI layer does now, what later tiers add, and where the boundaries stay explicit.
We keep the conversation scoped to the use case you actually care about.