Chrome Extension · Team passkey manager

Share one passkey.
Sign in as a team.

Passkeys made shared logins impossible — one device, one person. Coauth is the software authenticator that lets your whole team create, share, and use passkeys for the accounts you log into together.

Join the beta Encrypted · synced to your account · no ads, no tracking
Acme Ops · team vault3 members
01
login.salesforce.com
ops@acme.co
shared
02
admin.vendor.com
billing@acme.co
shared
03
dashboard.analytics.io
team@acme.co
shared
3 shared passkeys · every member signs in with the same key
The Problem

Phishing-resistant MFA broke the shared login.

Salesforce, admin panels, vendor dashboards — more of them now require passkeys. A passkey lives on one device and can't be handed over, so the one shared account your team relies on suddenly only works for one person. Coauth gives the whole team a way to use it.

How It Works

Share a login in three steps.

01

Sign in with Google

Your encrypted vault opens automatically. One gate, nothing else to remember.

02

Create a passkey — pick a team

On any site, choose "create a passkey." Coauth's overlay saves it to you, or straight into a team.

03

Your team signs in

Members use the shared passkey from their own browser and their own account. No password ever changes hands.

Features

Made for shared logins, not solo vaults.

01

Built for sharing

Personal passkey managers lock a credential to one device on purpose. Coauth is designed so a whole team can use one passkey — with invites, roles, and a shared vault.

02

Real revocation

Remove a member and the team key is rotated automatically. Their access ends for real — not on the honor system, not "please stop using it."

03

One place to manage it

Your passkeys, your teams, who is a member, and an activity log of everything shared, joined, and used. All from one popup.

04

Encrypted vault, synced

Credentials are encrypted with audited cryptography (libsodium) and synced to your account, so they are there on every device you sign in on.

05

Nothing to pass around

No exported password in a chat thread. No shared spreadsheet of logins. The credential itself moves, encrypted, to the people you choose.

06

Works with the sites you use

Any site that supports passkeys — from a shared Salesforce org to an admin console or vendor dashboard.

Straight Talk

What Coauth is — and isn't.

Coauth can only share passkeys it creates; an existing device or security-key passkey can't be exported (that's the point of passkeys), so you add a new one through Coauth. Only one passkey extension runs at a time, so Coauth has a one-click Pause when you need your device's own passkeys. Your vault is encrypted before it's stored or synced — and we're moving to a design where only you can unlock it, not our servers. We'll say so here the day that ships.

FAQ

Common questions.

Can Coauth share a passkey I already have?
No — a passkey registered with your fingerprint or a security key can never be exported. That is the whole security model of passkeys. To share one, you add a new passkey to that account through Coauth, and Coauth shares that.
Is it a password manager?
No. Coauth is focused on one thing: letting a team share and use passkeys for accounts they log into together. It does not store passwords, generate them, or autofill logins.
How do I revoke someone?
Remove them from the team. Coauth rotates the team key so any copy they had can no longer decrypt the shared passkeys.
Does it work alongside 1Password or Proton Pass?
Only one passkey extension can be active in the browser at a time. Coauth has a one-click Pause so you can hand control back to another authenticator when you need it, then resume.
What does it cost?
Free while in beta.

Give your team one login they can all use.

Free while in beta.