UbID Product Portfolio
The UbID Trust Fabric is organized as a portfolio of product domains. Each product addresses a distinct part of the digital-trust lifecycle, while shared policy, cryptographic, interoperability, and evidence capabilities connect the portfolio into one governed platform.
A product name identifies a responsibility. It does not imply that every capability is enabled in every deployment, available in every jurisdiction, or included in every commercial agreement.
Product families
| Product family | Products | Primary purpose |
|---|---|---|
| Identity and credentials | UbID Proof, UbID Credential Cloud | Establish identity evidence and issue governed credentials. |
| Holder control and continuity | UbID Wallet, UbID Recover | Protect credentials, manage consent, and restore continuity under guarded authorization. |
| Access and interoperability | UbID Access, UbID Connect, UbID Trust API | Authenticate users, connect trust domains, and expose governed integration contracts. |
| Security and operations | UbID KeyVault, UbID Pulse, UbID Sentinel AI | Protect cryptographic operations, observe platform posture, and assist evidence-based operations. |
Portfolio at a glance
| Product | Public role | Typical users |
|---|---|---|
| UbID Credential Cloud | Issue and manage verifiable credentials. | Issuers, institutions, partners |
| UbID Proof | Evaluate identity and document evidence. | Onboarding, risk, and verification teams |
| UbID Access | Provide adaptive authentication and secure access. | Workforce and customer-access teams |
| UbID Wallet | Protect holder-controlled credentials and consent. | People, organizations, wallet participants |
| UbID Recover | Restore identity and wallet continuity through guarded recovery. | Holders, security teams, recovery participants |
| UbID Connect | Enable interoperability and trusted messaging. | Ecosystems, integrators, partner institutions |
| UbID KeyVault | Govern institutional keys and cryptographic operations. | Security teams, auditors, platform operators |
| UbID Trust API | Expose developer-facing trust capabilities. | Developers and authorized partners |
| UbID Pulse | Correlate health, trust, security, and operational evidence. | Operations, security, and governance teams |
| UbID Sentinel AI | Assist interpretation of operational evidence under guardrails. | Authorized operations and decision teams |
How the products work together
A typical credential flow may involve several products:
- UbID Proof evaluates identity, document, or assurance evidence.
- UbID Credential Cloud applies issuer policy and creates a signed credential.
- UbID Wallet receives and protects the credential under holder control.
- UbID Connect and UbID Trust API support standards-based exchange.
- A verifier evaluates the presentation, issuer, status, holder relationship, and transaction policy.
- UbID KeyVault protects institutional signing and encryption operations.
- UbID Pulse records service posture and operational evidence.
- UbID Recover supports continuity when access or devices are lost.
- UbID Sentinel AI may help authorized teams interpret evidence, while deterministic services remain authoritative.
Product boundaries
Clear boundaries prevent a convenient user interface or operational tool from silently becoming the authority for trust.
- Experience channels present information and collect intent.
- Domain services validate policy and determine whether an operation is permitted.
- Cryptographic services perform narrowly authorized operations.
- Holders authorize presentations and manage their credentials.
- Issuers remain responsible for the claims they issue.
- Verifiers and relying parties remain responsible for their acceptance and business decisions.
- Operations and AI capabilities observe, explain, and prioritize; they do not silently alter authoritative state.
Choosing a starting point
Institutions commonly begin with one of four entry points:
- Issue trusted evidence: start with UbID Proof and UbID Credential Cloud.
- Accept portable credentials: start with verifier integration through UbID Trust API and UbID Connect.
- Protect holder continuity: start with UbID Wallet and UbID Recover.
- Strengthen institutional control: start with UbID KeyVault and UbID Pulse.
The architecture is modular, but trust is end to end. A successful deployment still requires role allocation, policy, key governance, privacy controls, operational evidence, and recovery planning.
Availability terminology
Public documentation uses controlled availability language:
- Available — supported for a defined production scope.
- Limited availability — production use with stated constraints.
- Preview — available for evaluation with limited commitments.
- Planned — approved for future development or rollout.
- Conceptual — architecture or product concept under evaluation.
- Partner access — available through controlled onboarding.
Current availability must be confirmed for the intended deployment, jurisdiction, sector, and contract.