Skip to content

Biometric Authentication

Bind accounts to actual people.

A woman walks out of an office lobby, speaking into her phone

Helix uses the human voice to tie a real person to an account in about four seconds. Zero biometric data leaves the device which means zero compliance overhead.

The problem

Authentication is broken for the AI era.

Login factors prove strings, numbers, or devices, not people.

  • Passwords

    People reuse passwords. One leak opens many accounts.

    Stolen passwords show up in more than a third of breaches. With a voice check, there’s nothing to type or phish, and a recording or a cloned voice won’t get through.

  • A woman carrying groceries up a staircase gets an "Approve sign in?" prompt

    MFA itself

    MFA security can be bypassed for the right price

    Barracuda found MFA bypass in 48% of the phishing attacks it tracked through 2025. The bypass is off the shelf: the number of known phishing kits doubled over the year, and 90% of high-volume campaigns ran on a kit somebody else built and sold.

  • Phone numbers

    A banned user can buy a new number

    A phone number only tells you someone has a SIM card. If you ban the account, the same person can sign up again with a new number that costs a few cents. Helix ties the ban to their voice, so a new number won’t get them back in.

The problem

Attackers spoof devices. They cannot spoof people.

Every factor in a normal login stack proves something other than a person. A password proves a string. An SMS code proves a number. A passkey proves a device.

Attacker Cost Today

  • $0.10

    a phone-verified social media, dating or e-commerce account

  • $0.10

    an SMS verification in the UK. Twenty-six cents in the US.

Cambridge researchers spent a year pricing this market. Devices go by the hour, residential proxies by the gigabyte, eSIMs and numbers by the unit. All rented, all disposable, all running at the same time.

Attacker Cost With

  • Each fake account needs a real person, paid and ready to say the numbers out loud every time a check comes up.

  • If the same voice tries to sign up again, Helix flags it.

Bots are cheap to run at scale. People aren’t. Each extra account needs another person to take the check live, so a thousand fake accounts means finding, paying, and scheduling a thousand people.

How it works

Four seconds of speech.

The user says four numbers. The SDK builds the voice template, matches it in the secure enclave, and hands your server one signed verdict without audio or PII.

A man leaning on his kitchen counter speaks into his phone

Why on-device matters

Server-side biometrics are a liability.

Server-side biometrics are a liability. One company paid $650 million to settle a single biometric privacy class action. Helix keeps the data on the user's device, so you never hold it.

How it works

  1. Capture

    The user says four numbers, about four seconds, on any device with a microphone.

  2. Verify

    The device turns the voice into a voiceprint, and Helix matches it against the one on file. The recording never leaves the device.

  3. Prove

    Your server gets one signed result and a stable ID for that user.

  • Passive liveness rejects replays and synthetic voices
  • No audio uploaded
  • No selfies, ID uploads, or cameras required.
  • Open proof format — audit any verification

Cross-account enforcement

One person. One account.

  • Strict mode

    One human, one account

    Best for signup: a server-side voiceprint hash stops the same human enrolling twice.

  • Soft signal

    Collision detection

    Best for transactions and trust scoring: flags a match against an existing identity and lets you block, review, or just log it.

  • Device only.

    Pure on-device mode

    Default everywhere else: binding, liveness, and signed proofs, nothing stored — no new disclosure, but it can't flag a repeat human.

Integration

Three lines. Bound.

Bind a user in under 5 minutes.

Get the SDK
// biometric-sdk.js
  1. Drop the tag on any page

    <script src="https://cdn.jsdelivr.net/npm/@helix-id/browser@0/dist/helix.iife.js"></script>
  2. Enroll once at signup

    Helix.open({ startUrl: "/helix/enroll", onSuccess: saveUser });
  3. Verify on any high-risk surface

    Helix.open({ startUrl: "/helix/verify", onSuccess: grant });

Your server signs each start with @helix-id/node.

Bind your users. End takeover.

We'll integrate Biometric Authentication into your highest-risk flow in under a week. No PII touches your servers. No passwords to lose.