Skip to main content
Public website
Public website surface Marketing and explanation content. This is not the canonical authenticated runtime.
Canonical runtime: app.identityfirst.net
Platform overview

Start with clarity. Grow into ongoing control only when you need it.

IdentityFirst is built around a simple progression. Start with IdentityFirst MRI for a read-only exposure review, then move into IdentityFirst Core only if you need recurring governance, with IdentityFirst Enhanced and IdentityFirst AISF kept as later private-beta layers.

It is not about implying that every layer is broadly available today. It is about giving buyers a credible first step, an honest controlled rollout path, and a clear view of what remains later-stage.

What buyers usually need

  • A low-friction first review they can approve quickly.
  • A clearer way to explain access risk to operators, boards, and auditors.
  • An ongoing rhythm if they want reporting and governance after the first assessment.
  • A platform that can grow with them rather than forcing a tool change later.

Four-product progression

Start with proof. Expand only when you need more.

The shared foundation stays the same. What changes is how much regular review, guidance, and bounded, human-governed orchestration you want around it, and whether that layer is GA, controlled rollout, or private beta today.

Diagram showing MRI, Core, Enhanced and AISF sitting on top of a shared Substantia substrate.
The image carries the hierarchy quickly: one platform, four product layers, and one substrate beneath them.
GA now

IdentityFirst MRI

The public entry point: a read-only review of access exposure, stale permissions, and the clearest first action.

Best for: getting a clear starting point without changing customer systems.

View MRI
Controlled rollout

IdentityFirst Core

The governed next step for recurring review, reporting cadence, and tighter operating control.

Best for: customers who want ongoing reporting, trend tracking, and service rhythm.

View Core
Private beta

IdentityFirst Enhanced

Extra guided analysis and deeper decision support for approved later-stage pilots.

Best for: customers who want more help deciding what to do next.

View Enhanced
Private beta

IdentityFirst AISF

The most advanced layer for bounded, human-approved action workflows in approved programmes.

Best for: later-stage accounts that want more governed action, not a first purchase.

View AISF

How the platform fits together

Each part of the platform has a different job.

Most buyers do not need deep architecture detail. They just need to know why the website, working portal, rules layer, and shared foundation do not contradict each other.

Website and demo

This is where the company explains the offer, shows representative journeys, and sets honest expectations.

Working portal

This is where operators and customers use the live product for runs, reports, governance, and follow-up work.

Rules and workflows

This is where approvals, governed workflows, connector execution boundaries, and service control are handled behind the scenes.

Shared foundation

This is what keeps access data, findings, evidence, and later actions working from the same picture rather than drifting apart.

What the platform is not

Blast radius is important. It is not the whole company story.

IdentityFirst spans identity discovery, governance, evidence, reporting, assisted analysis, and guarded action workflows. MRI does not need to promise the full depth of every later layer to be a credible public starting point.

Understand Substantia See the MSP story