Passwordless, from laptop login to production.
Most passwordless projects stop at the browser. Bastyx carries the same phishing-resistant identity to workstation login, SSH, internal apps and legacy apps that only know passwords, using passkeys, security keys and the biometric sensors your team already has.
The Bastyx USB-C fingerprint reader. Optional; standard FIDO2 keys work too.
What “passwordless” should mean
Replacing a password with a one-time code sent by text isn’t passwordless in any meaningful sense: there’s still a secret a person can be tricked into typing. Real passwordless authentication uses public-key cryptography through the FIDO2 standards.
- At registration, the person’s authenticator creates a key pair. Only the public key is shared.
- At sign-in, the service sends a random challenge.
- The person confirms locally, with a touch, a PIN or a fingerprint matched on the device.
- The authenticator signs the challenge, bound to the service’s domain, and the service verifies it.
Nothing secret crosses the network or sits in a database, and a signature for the real domain can’t be produced on a phishing site.
FIDO authentication and the shift to passwordless security
For years, stronger authentication meant stacking something on top of a password: a text message, an app code, a push prompt. Each layer helped, and each one still depended on a person handing over something an attacker could reuse. Real-time phishing kits now relay passwords and one-time codes as fast as people type them, and push prompts get approved just to make them stop.
FIDO2 changes the model instead of adding a layer. There’s no shared secret at all, so there’s nothing to type into the wrong page, nothing to read out over the phone and nothing useful in a breached database. That’s why the major platforms now build passkeys in, and why security standards increasingly ask for phishing-resistant authentication by name.
| Password | Password + code | FIDO2 | |
|---|---|---|---|
| Resists look-alike sites | No | No, codes can be relayed live | Yes |
| Nothing a person can be talked into sharing | No | No | Yes |
| No reusable secret on the server | No | No | Yes |
| Proof a person is physically present | No | No | Touch or on-device biometric |
| What people do | Remember, type, reset | Type, then copy a code | Touch a key or a sensor |
Resists look-alike sites
- Password
- No
- Password + code
- No, codes can be relayed live
- FIDO2
- Yes
Nothing a person can be talked into sharing
- Password
- No
- Password + code
- No
- FIDO2
- Yes
No reusable secret on the server
- Password
- No
- Password + code
- No
- FIDO2
- Yes
Proof a person is physically present
- Password
- No
- Password + code
- No
- FIDO2
- Touch or on-device biometric
What people do
- Password
- Remember, type, reset
- Password + code
- Type, then copy a code
- FIDO2
- Touch a key or a sensor
Why FIDO2 is AI-agent resistant
AI hasn’t changed what a password is. It has changed how cheaply someone can be talked out of one. Generated emails read like they came from your finance team, a cloned voice can pass for a colleague, and autonomous agents can run login attempts around the clock. Every one of those attacks still ends by asking a person, or a login form, for a secret.
FIDO2 takes that secret away. An agent can’t touch a security key or pass a fingerprint check on a device it doesn’t hold, and a page it generates can’t get a signature for your real domain. Bastyx adds recovery that requires admin approval and a second registered authenticator, so a convincing call to the help desk can’t reset anyone’s access, and separate identities for the AI agents you run, so they never need a person’s credentials.
FIDO2 protects the sign-in itself. Bastyx also checks the device and keeps infrastructure sessions short, because a session on a compromised machine is a different problem.
Passkeys, security keys and biometrics
They’re complementary, not competing. Most teams use device passkeys day to day and hardware keys for sensitive access.
| Synced passkey | Device-bound passkey | Security key | |
|---|---|---|---|
| Phishing-resistant | Yes | Yes | Yes |
| Private key can’t be copied | Synced by platform | Yes | Yes |
| Survives losing a device | Yes | No | No |
| Extra hardware | No | No | Yes, per person |
| Biometric option | Device sensor | Device sensor | On some models |
| Best for | Everyday app sign-in | Managed laptops | Admins and production |
Phishing-resistant
- Synced passkey
- Yes
- Device-bound passkey
- Yes
- Security key
- Yes
Private key can’t be copied
- Synced passkey
- Synced by platform
- Device-bound passkey
- Yes
- Security key
- Yes
Survives losing a device
- Synced passkey
- Yes
- Device-bound passkey
- No
- Security key
- No
Extra hardware
- Synced passkey
- No
- Device-bound passkey
- No
- Security key
- Yes, per person
Biometric option
- Synced passkey
- Device sensor
- Device-bound passkey
- Device sensor
- Security key
- On some models
Best for
- Synced passkey
- Everyday app sign-in
- Device-bound passkey
- Managed laptops
- Security key
- Admins and production
One identity across every surface
macOS and Windows workstation login
Sign in with a passkey, security key such as a YubiKey, or fingerprint instead of a password.
Linux workstation login
Passwordless desktop login and sudo, backed by the same identity.
SSH and servers
Short-lived, identity-bound access with a security-key touch.
Internal applications
Single sign-on to the tools your team runs, with step-up where it matters.
Legacy applications
Apps that only accept passwords, through SSO, an access proxy or a vaulted credential nobody knows.
Biometrics stay on the device
With FIDO2, a fingerprint or face is matched by the authenticator itself. The service only receives a signature showing that verification happened. Bastyx never receives or stores biometric data, and biometrics are always one option among several, never a requirement. For machines without a built-in sensor, the Bastyx USB-C fingerprint reader adds one with a single plug.
Passwordless questions
What’s the difference between a passkey and a security key?
Both are FIDO2 credentials. A passkey usually lives on a phone or laptop and may sync between a person’s devices through their platform account. A security key is a separate piece of hardware whose credentials stay on that key. Security keys give the strongest guarantee that a credential can’t be copied; synced passkeys are easier to recover.
Are passkeys really phishing-resistant?
Yes. A FIDO2 credential is bound to the domain it was registered for, and the browser or operating system enforces that. A look-alike domain can’t request a signature for the real one, so there’s nothing for a person to be tricked into handing over.
Can AI-generated phishing or deepfakes get past passkeys?
Not by stealing the credential. A passkey is bound to the real domain and never leaves the device, so there’s nothing for a generated email, a cloned voice or a fake login page to collect. Attackers go after account recovery instead, which is why Bastyx recovery requires admin approval and a second registered authenticator.
What if someone loses their only authenticator?
That’s why every person should register at least two. Recovery in Bastyx requires admin approval and a second registered authenticator, so recovery can’t become the weak point.
Do we need special hardware?
No. Most modern laptops and phones can hold passkeys, and Bastyx works with standard FIDO2 security keys. Laptops without a fingerprint sensor can add the optional Bastyx USB-C fingerprint reader. Hardware keys are recommended for administrators and production access.
Bring every login, key and server under one control layer.
Tell us what you’re securing and see Bastyx live in 20 minutes. We reply the same business day.