A secure bridge from vault to field

Extend one key, not the keyring.

Why copy an entire password vault to every computer just to use one credential? Passkeys are improving that model, but passwords, usernames, and recovery codes remain. Fill from Phone keeps the keyring on your phone and sends only the value you choose.

A phone scans a QR code beside a selected field on a laptop, then sends the value into that field.

Chrome Web Store · Coming soon

The current Chrome release is available on GitHub.

Download version 0.6.2 for Chrome 120 or newer, or review the source and release notes before installing.

One credential crosses. Your vault does not.

The desktop asks for one value. Your phone supplies only that value through a fresh encrypted path.

A complete laptop with a selected browser field beside a one-time QR code and phone.
1

Choose the field

Right-click the exact password or editable field that needs the value.

A phone scans the one-time QR code and sends a value to the selected browser field.
2

Scan

Your phone opens a short-lived encrypted path bound to that field.

3

Send one value

Bring it from your phone's password manager. The desktop receives only what you send.

Passkeys are the direction. Password fields are still everywhere.

Fill from Phone covers the awkward middle: a strong credential is already protected on the phone, but the computer still needs it and does not need the entire vault.

Computers without the vaultSites without passkeysLong generated passwordsTemporary browser sessionsCross-platform sign-ins

A secure handoff primitive—not another password manager.

The reference extension proves a narrow phone-to-field interaction. The underlying protocol can fit inside an existing trusted mobile client and signed browser extension, extending a vault's reach without cloning the vault onto another endpoint.

One requested field. One authorized value. One consumable delivery. The proprietary technology is available for confidential technical diligence, commercial integration, and licensing.

The relay moves the envelope. It cannot read the message.

Your phone encrypts the value for the browser extension. The service holds only the opaque envelope long enough to deliver it once, and the extension never submits the form for you.

2 minutes
maximum route lifetime
1 scan
first phone claims the transfer
1 delivery
the encrypted envelope is consumed once

Chrome Web Store · Coming soon

Keep the vault on your phone.

View the current release on GitHub