Product status and read-only assurance
This page exists for one reason: to make it obvious what is GA now, what is controlled rollout, what is private beta, and how the platform behaves when it first looks at your environment.
What is live now
A simple status view for boards, MSPs and procurement teams using the same public labels everywhere else on the site.
Read-only assessment
We start by observing and explaining. That means you can see the value without first approving changes to your systems.
Current public product path
IdentityFirst MRI is the only public GA surface today. IdentityFirst Core is a controlled rollout path for approved deployments. IdentityFirst Enhanced and IdentityFirst AISF remain private beta, and the public experience should make those boundaries obvious.
Source-mode cues
Use runtime-backed language only where the proof is actually live. Curated demo routes and representative report outputs are labelled as such and should not be presented as live tenant proof.
Customer-controlled action
If a customer later asks for actioning, that remains explicit and human-approved. Nothing is silently changed behind the scenes.
Current stage by product
A plain-English summary you can repeat in a live conversation.
| Product | Status | What that means |
|---|---|---|
| IdentityFirst MRI | GA now | The only public GA surface: read-only assessment, identity discovery, evidence-backed findings, and representative executive and technical report generation. |
| IdentityFirst Core | Controlled rollout | Recurring review, reporting cadence, and broader governance for approved deployments only. |
| IdentityFirst Enhanced | Private beta | Later-stage guided analysis and richer decision support in explicitly approved pilots. |
| IdentityFirst AISF | Private beta | Bounded, human-approved action workflows for approved programmes. |
| Substantia | Foundational | Shared identity and evidence substrate underneath the wider platform. |
What the labels mean
These are the public meanings behind the status labels.
Runtime-backed
Derived from live product or runtime state where configured and explicitly available.
Partial runtime
Mixes live signals with fallback or incomplete runtime evidence. Keep the caveat attached and avoid overstating completeness.
Curated demo
Representative walkthrough content and report framing, not live tenant state, customer evidence, or deployment proof.
Static statement
Human-maintained public wording used where runtime proof is not the right source and should not be inferred from demo/report output.
What to say to a buyer
Short lines that keep the conversation honest.
For boards
“We start with IdentityFirst MRI because it gives evidence without disruption. It is the only public GA surface. Wider layers are clearly marked as controlled rollout or private beta.”
For MSPs
“This gives you a credible MRI-led first service, then a reason to keep reporting and improving over time without presenting later layers as publicly available.”
For procurement
“The status is explicit: only MRI is GA now; Core is controlled rollout; Enhanced and AISF are private beta; Substantia is foundational. The boundary is clear, and the read-only promise is easy to explain.”