Phishing-resistant MFA. Without the MFA hassle.
Users sign in with the device they already have. There are no passwords, codes, push prompts, security keys, or second devices to manage.
MacOS Device · Secure Enclave
Every MFA method verifies the user once, at login. Then it stops checking.
Nothing re-checks the device. Nothing re-checks the session. The credential that comes out the other side is portable to any attacker’s machine.
Traditional MFA gets bypassed, and annoys people on the way
Push fatigue, codes, token taps, lockouts. Users approve prompts to make them stop, and attackers count on it. The playbook is now industrialized: personalized lures, fatigue bombing, and session hijacking that waits until after someone authenticates.
Passkeys fixed phishing and created new problems
Device-bound passkeys are hard to live with, which device, which passkey, re-enrollment, shared accounts, and users rather than admins in control. Synced passkeys fix the friction but lose the anchor: a key that syncs is a key that can be stolen. Either way, the device holding the key is blindly trusted.
FIDO2 proves a human is present. It does almost nothing to verify the device. Proving you hold a key isn’t the same as proving the device can protect the key.
Verify continuously. Interrupt users never.
Gradient turns on the platform security already built into your users’ laptops and phones. Nothing to buy, nothing for users to carry, nothing to type.
Nothing to phish, nothing to hand over.
No password, no code, no shared secret, no approval prompt. Login is bound to the device’s platform root of trust, so there is no portable credential for an attacker to capture, replay, or trick someone into approving.
Simpler than what you run today.
Users stop carrying keys, enrolling phones, reading codes, and approving prompts. Admins stop shipping hardware, replacing lost keys, and clearing lockouts. Self-service enrollment, phased by user group.
Every platform, not most of them.
Windows, Mac, Linux, iOS, and Android. Laptops, phones, virtual desktops, shared workstations. One lightweight client, deployed through the MDM you already run.
The session is anchored too.
Most phishing-resistant methods secure the login and leave the session token portable. Gradient anchors the session to the same device, which is what closes token theft and replay after authentication.
Attest, anchor, rotate.
Attest
The device is continuously verified down to its firmware and silicon. A compromised device holds no valid credentials.
Anchor
User identity, device identity, and the application session are bound to secure silicon: TPM, vTPM, or Secure Enclave. They cannot be exfiltrated.
Rotate
Credentials are re-attested and regenerated every ten minutes. Stolen material expires before it can be used.
Where Gradient plugs in
Self-service, by user group. Phased rollout.
Your conditional access, plus continuous device posture.
Lifetimes you set. Short enough to starve theft.
Nothing to install on your applications. No changes to your SSO.
What changes
Your IdP still owns its SSO session. What changes is the economics, when re-auth is free for the user, short sessions become practical.
Under an hour, as an overlay.
Gradient delegates from your existing IdP over SAML 2.0 or OIDC. No changes to your applications, no changes to your SSO configuration beyond the delegation itself, and no rip-and-replace. Roll out by user group at whatever pace you want.
Delegate.
Point your IdP at Gradient for the second factor. Under an hour.
Deploy the client.
Push it through Intune, Jamf, or your existing MDM. Linux packages and mobile apps available.
Enroll.
Users enroll themselves, by group, on a schedule you control.
Nothing for the user to install, carry, or open, one managed client, pushed through the MDM you already run.
Against what you’re probably evaluating.
Versus hardware keys
No device to buy, ship, replace, or lose. No lockouts when one goes missing. And the credential is anchored to a device you can attest, rather than to a token that works in any USB port.
Total cost of ownership comparison →Versus passkeys
Passkeys prove a human is present. They don’t verify that the device holding the key is uncompromised, and they don’t anchor the application session. Gradient does both, and enrollment and revocation are controlled by admins rather than by end users.
Versus other passwordless
Most solutions establish a device ID and stop there. Gradient anchors user identity, device identity, and the session, and re-attests continuously rather than trusting a one-time posture check.
Identity providers and client platforms
Deployed across 5 continents and 11 time zones.
Validated in extensive DoD red-team testing, with no side-channel vulnerabilities identified.
We meet industry-recognized standards for security, availability, and confidentiality, independently audited, so you can rely on us with confidence.
FIDO2 / WebAuthn · SAML 2.0 · OIDC
The same root of trust secures your AI agents.
Gradient for Users anchors identity to the verified platform. Gradient for Agents checks every agent action against it. One root of trust, everything above it inherits.