Human presence infrastructure
Verify who isreally presentbefore high-stakes actions execute.
Verify the person, device, and authority—then seal the proof before execution.
Live in production · Web SDK · REST API · Signed Presence Records
const result = await presence.verify({ intent: "meeting.participant.verify", evidence: ["video", "audio", "device"],});Authentication proves a credential. Presence proves the person is participating now.
Three proofs, answered before the action executes.
Proof of Device
A passkey assertion, verified server-side, whose challenge commits to the exact action being approved.
Proof of Presence
Pulse under the skin, a randomized screen-reflection challenge, and lip–voice alignment — scored on the weakest signal.
Proof of Authority
Policy turns that evidence into one of four verdicts, scaled to what the action is worth.
Live proof
Run it against a genuine presence, then against a synthetic one.
The demo runs the real engine in your browser. Switch the presence profile and watch the verdict change — then download the signed Presence Record it produced and check it offline against our published key.
- Genuine presence → AUTHORIZED
- Gray zone → ESCALATE, with a step-up
- Synthetic presence → BLOCKED, sealed
Verify at the moment trust becomes irreversible.
All use cases →Developers
Your first Presence Record, in minutes.
Create a sandbox
Work email in, isolated tenant and server key out — shown once, on landing.
Send the intent
Open a session with the action context: intent, actor, amount, target.
Run the check
The browser SDK does capture and analysis in the page. Pixels never leave it.
Receive the Presence Record
One decision call returns the verdict and the signed record together.
Verify the signature
Offline, against our published key, with a ~100-line script you can read.
See what Presence would have challenged, before it challenges anyone.
In watch-only the verdict is computed and sealed exactly as it would be in enforcement — only the answer given to your system is softened. That is what makes a shadow period a measurement rather than a gap.
Shadow-mode methodology →Every claim here has an artifact behind it.
Meet the action where it begins.
All surfaces →- Web SDK
- REST API
- Biometric + liveness checks
- Signed Presence Records
- Watch-only rollout, one-click back
- Meeting + identity connectors
- iOS & Android approver approlling out
The security review, without a meeting.
What leaves the browser, what happens when Presence fails, and who can see what — answered in public, including the answers that are no.
Readiness is stated, not implied.
Every surface and every page on this site wears one of four labels. Where something is planned rather than shipped, the page says so in its own words.
Questions we are asked first.
What is Human Presence Infrastructure?
A verification layer that banks, apps, and video calls check before trusting anyone — think of it as a CAPTCHA for the person rather than the browser. Your system calls Presence when something consequential is about to happen, Presence asks the human to prove they are live and really themselves, and you get back a verdict and a signed record.
Who does Presence verify today?
Presence verifies people today. It checks the device they are on, whether a live human is really there, and what they are trying to do — then signs a record of the decision that you can verify yourself.
Can the trust model extend beyond humans?
The same question applies when an AI agent, a device, or a wallet is acting instead of a person, and that is where we are heading. None of it is available yet, and we would rather say so here than in a procurement call.
Where can Presence enter an existing workflow?
Your own web app, Zoom, Microsoft Teams, Slack, Webex, Okta and SAP. You connect one by signing in to it — the install provisions itself, and the controls we can use on each platform are already validated on our side.
Put Presence in front of one consequential action.
Start in watch-only, on one workflow. Nothing is blocked while you measure what would have been challenged — and one request puts it back.