No password to create, remember, reset or steal. Members sign in to your site by approving on their own phone or watch, confirmed with face or fingerprint. Nothing to type, so a look-alike page has nothing to collect. And every sign-in arrives as a trusted connection.
No password, no code, no button to find. A sign-in starts with a single tap from wherever you are, and your face or fingerprint finishes it.
Everyone has had one of these moments. Most of them come from the same place: a secret that can be guessed, copied, phished or lost.
There is no password to leak.
Nothing to remember and nothing to reset.
Nothing to type, so a fake page has nothing to collect.
Approvals go only to the phone you enrolled, with your face or fingerprint.
Every sign-in is one person approving on a phone that is theirs.
No resets, because there is nothing to forget.
Your site keeps no passwords and no secrets worth stealing.
Every enrollment opens a Connection you keep.
The real thing on Apple Watch. Come back to a site you’ve signed in to before and the request goes to your wrist: the number matches, one tap signs you in.
Members use whichever way fits the moment. The site never asks them to type a secret.
A sign-in request appears on the phone. Approve, with face or fingerprint when the site requires it.
For moments when a scan isn’t practical. The code goes into the Linxy App, never into the website.
The site shows a number and the phone confirms the same one. A wrong number cancels the sign-in.
Where other sites show a password box, yours shows an image you chose: your artwork, your building, your banner. Only the Linxy App can read it, and the confirm number beneath it ties the sign-in to the screen in front of the member.
When the sign-in page is open on the same phone, the member taps the image instead of scanning it, then approves with face or fingerprint.
These are demonstration sites. Every name and record on them is invented.
Each site sees its own private identifier for a member, never their details and never their other sites. Linxy never sees or keeps login credentials, because there aren’t any.
id · 7f3a…c21id · 2b90…e4did · c51e…08aOne verified person, three unrelated identifiers. Built on Linxy Fusion™, patent pending.
Passkeys are strong, well-built security, and they remove the password too. The difference is what sits behind the sign-in, where it works, and what your site has afterward.
| Passkeys | LinxyPass™ | |
|---|---|---|
| Where it lives | A key stored in a password manager on the device: Apple’s, Google’s or a third party’s. | An approval in the Linxy App on the member’s own phone, the same app on iPhone and Android. |
| Signing in on a computer | If the computer doesn’t hold the key, it shows a QR code, the phone scans it, and Bluetooth checks the phone is nearby. | Scan the site’s own sign-in image, tap the notification, approve on the watch or type a 6-digit code into the app. No QR code, no Bluetooth pairing. |
| Changing phones | Keys sync inside one ecosystem. Moving between Apple and Android takes extra steps. | Sign in to the Linxy App on the new phone, enroll it, and revoke the old one from the Linxy account. |
| Face or fingerprint | The site can ask for verification; the device decides how, and a screen-lock PIN can satisfy it. | At the biometric level, face or fingerprint every time, enforced on Linxy’s servers. |
| Shortcuts | The device’s own sign-in prompt. | One tap on Apple Watch or Wear OS, or from a tile on the home screen. |
| What your site gets | A sign-in for that site. | A private identifier for that site, plus a verified person and a Connection you keep, built on Linxy Fusion™ (patent pending). |
| Adding it | Your developers implement WebAuthn, or you buy it from an identity vendor. | A WordPress plugin, a PHP kit, a JavaScript SDK or a few calls from your own code. |
Apps like KeePass or 1Password store passwords so people don’t have to remember them. The password still exists, can still be phished, and your site still has to keep and protect it. LinxyPass has no password to store anywhere.
Yes. LinxyPass runs alongside whatever sign-in you have today, so members who already use passkeys or passwords can keep them while others switch.
Passkey details: Google for Developers, “Passkey use cases” (cross-device sign-in by QR code with Bluetooth proximity); Corbado, “Synced passkeys cross-platform” (sync stays within an ecosystem).
A tap on the wrist.
You’re signed in.
Apple Watch and Wear OS, for browsers that already remember the member.
Every phone and tablet that can approve a sign-in is listed in the member’s Linxy account, with when it enrolled and when it last signed in. One click revokes it. Enrolling a new one takes a moment.
Tap to approve on the phone or watch. Best for member sites, communities, dashboards and everyday sign-ins.
Scan the site’s LinxyPass image plus face or fingerprint, every time. For sites where every entry must re-verify the person.
Set up once. You receive a public Partner ID for your pages and a partner key and webhook secret that stay on your server.
At lnxy.me/partner/start, sign in with your Linxy account and name your site.
LinxyPass runs on the site you control, and only there.
Pick a starter image or upload your own artwork. It becomes your site’s LinxyPass image.
Members turn on LinxyPass from their account, or enroll on their first scan if you allow it. Every sign-in after that is a verified person.
Install it, choose your sign-in image, and the login page shows LinxyPass. Turn on “LinxyPass only” to hide the username and password form, with a small “Sign in with a password” link kept for emergencies.
For plain PHP sites, with adapters for CodeIgniter 3 and AltumCode apps. Sign-in finishes through your site’s own session, so nothing is reimplemented.
One tag renders the sign-in button and panel, starts the session, shows the image or code and waits for the approval.
Start a session, show the image or code, confirm it on your server with your partner key. Signed webhooks report each confirmed sign-in.
Drop it on any sign-in page. When a member approves, your server confirms the session with your partner key and signs them in to the account linked to their private identifier.
Never sign anyone in from the browser’s word alone. The confirmation always happens on your server.
<div data-linxypass data-partner-id="lp_0123456789abcdef"
data-on-success="onLinxyPass"></div>
<script src="https://lnxy.me/static/linxypass.js"></script>
<script>
function onLinxyPass(result) {
// Send result.session_id to your server and confirm it there.
}
</script>Each one accepts anyone with the Linxy App. Open it on a computer, tap sign in, and scan the image.
No separate LinxyPass fee. Members always sign in free with the Linxy App®.
Your Recovery Mark is a card you keep somewhere safe. If your phone is lost or stolen, it moves your Linxy account to your new phone in minutes.
No password, no number, no code is printed on it. On its own a Recovery Mark is worthless: it only works together with your biometrics and access to your email account.
Passkeys are keys kept in a device’s password manager; signing in on another computer means scanning a QR code with Bluetooth nearby, and keys don’t move easily between Apple and Android. LinxyPass is an approval in the Linxy App on any phone, with watch and home-screen shortcuts, an optional face-or-fingerprint check every time, and a verified person and Connection behind every sign-in.
No. It’s a Linxy Mark: an image only the Linxy App can read. A phone camera on its own sees a picture, not a link, so there’s nothing to copy or swap.
A private identifier that belongs to your site alone. It is different on every site, so sites can’t compare notes, and it carries no name, email or other sites.
There aren’t any. Members approve on their own phone or watch, confirmed with face or fingerprint when the site requires it. Linxy never sees or keeps login credentials.
They move their account to the new phone with their Recovery Mark, their email and their face or fingerprint, then revoke the old phone from their Linxy account. Every device is listed with when it enrolled and when it last signed in. How recovery works
No. Members sign in free with the Linxy App®.
Yes. Run LinxyPass alongside your existing sign-in, or on WordPress turn on “LinxyPass only” and keep a small password link for emergencies.
A paid Linxy plan and a site you control. Use the WordPress plugin, the PHP kit, the JavaScript SDK or your own code. The plugin and kit are on your LinxyPass setup page and dashboard.
Yes. Three demonstration sites, a shop, a school and a clinic, accept anyone with the Linxy App. Open one, scan its sign-in image, and approve.
Add LinxyPass to your site, or get the Linxy App and sign in with a glance.