Introduction
A guide to verified-human identity, live presence, and approval tied to a specific action.
VULT Security focuses on a simple question: which person is participating in a protected action, and what did that person approve?
Start with the person
An account login establishes that an accepted authentication method was used. A sensitive action can require more: confirmation that the human linked to an established identity is present at that moment. VULT Security calls that person a verified human.
VULTid is the reusable identity in this model. Enrollment connects a government-issued identity document to the live person through document validation, face matching, and liveness checks. Each later VULTid authentication or authorization calls for fresh liveness and server-side matching against that established identity. The organization decides which interactions require VULTid verification.
Understand verified-human identity
Connect approval to the action
Identity and presence alone do not say which transaction or change a person approved. Event-and-Identity-Bound Authorization connects the verified person's explicit decision to the action and its material details. The organization still decides who has permission and whether the action proceeds.
Explore event-bound authorization
Explore this guide
- Capabilities overview maps the core identity, presence, authorization, and evidence concepts.
- Device biometrics vs VULTid explains why a local device unlock and a check against an established identity answer different questions.
These pages explain product concepts. They do not specify an API, SDK, deployment process, or compliance guarantee.