← All products

Access control

Phishing-Resistant Authentication

Available now

Authentication bound to hardware the user is holding — not to a secret that can be phished, relayed, guessed, or synthesised.

Shipping today. Ask for access and we will get you a build.

What it does

A hardware gate on every privileged action

Touch ID or the device password, presented by the operating system itself, required before any privileged operation proceeds. Fail-closed by design: no timeout, no override flag, no bypass path.

Nothing an attacker can capture

There is no shared password to reuse, no one-time code to relay, and no voice or face sample accepted as a factor. A convincing synthetic likeness is not a credential here, because a likeness was never the credential.

Refuses rather than degrades

On a platform with no hardware authenticator available, operations are refused outright instead of silently falling back to something weaker. The weak path does not exist to be forced onto.

Pinned device identity

Enrolled devices carry a pinned certificate with a fixed validity window, so a stolen session presented from an unenrolled device does not authenticate.

Staged approval for high-value operations

Root and signing key transitions run as prepare, submit, then adopt — with operator evidence recorded at each stage, so no single compromised session can complete one alone.

Request Access

Why AI does not help here

The attacks that got cheaper have nothing to work with.

Credential stuffing
No password to reuse
Phishing page
Nothing to capture
Synthetic voice or face
Not an accepted factor
One-time-code relay
No code is issued
Stolen session token
Certificate-pinned

How it goes in

Each step is a checkpoint you sign off before the next begins.

  1. 01

    Enrol

    Devices enrol against your authority and receive a pinned certificate with a defined validity window.

  2. 02

    Gate

    Privileged operations call the hardware authenticator and block until the user responds. There is no path that proceeds without one.

  3. 03

    Approve

    High-value operations are staged across separate approvals, each recording operator evidence before the next can begin.

  4. 04

    Audit

    Every gated operation and every approval stage is recorded, so the question of who authorised what has an answer.