Welcome to UbID
UbID is a governed digital trust fabric for establishing identity, issuing and holding verifiable credentials, presenting proportionate evidence, verifying trust independently, and maintaining continuity through protected recovery.
Digital identity is often implemented as a collection of isolated accounts. Each organization asks the same person to register again, submit the same documents again, and depend on another password and recovery process. This creates duplication, concentrates personal data, and makes trusted information difficult to reuse.
UbID takes a different approach. It treats identity as a set of verifiable relationships among people, institutions, credentials, devices, cryptographic keys, and policies. The objective is to let trustworthy evidence move between compatible participants while preserving individual control and institutional accountability.
What this documentation explains
This portal presents the public functional and architectural model of UbID. It explains:
- how issuers, holders, wallets, verifiers, and relying parties work together;
- how verifiable credentials can carry trustworthy institutional claims;
- how selective disclosure can reduce unnecessary exposure of personal information;
- how authentication, device security, recovery, and continuity support long-lived identity;
- how privacy, security, interoperability, and operational evidence are governed;
- how organizations can approach integration without exposing internal systems or secret material.
Explore by objective
| Objective | Start here |
|---|---|
| Understand the overall model | What Is UbID? |
| See the issuer–holder–verifier flow | How UbID Works |
| Understand who is responsible for what | Roles and Responsibilities |
| Learn about portable digital identity | Digital Identity in UbID |
| Understand credentials and selective disclosure | Verifiable Credentials and Selective Disclosure |
| Review the public product family | UbID Product Portfolio |
| Explore privacy, security, and recovery | Trust, Privacy, and Security |
| Review open standards and interoperability | Standards and Interoperability |
| Understand public integration boundaries | Build with UbID |
Public documentation boundary
This portal is intentionally informative without exposing sensitive implementation details. It does not publish production topology, internal infrastructure addresses, private database structures, customer configurations, cryptographic key material, recovery shares, operational credentials, incident runbooks, or unresolved internal risks.
Availability statements are also controlled. A product name, design objective, or reference architecture does not by itself mean that every capability is generally available in every deployment. Capability status is described separately as Available, Limited availability, Preview, Planned, Conceptual, or Partner access.
UbID documentation explains what trust capability is provided, who is responsible for it, what evidence is exchanged, and where the governance boundary lies. It avoids publishing details that would weaken security or disclose customer-specific architecture.