An Authy alternative for teams

Authy is a good authenticator app for one person. The trouble starts when a team uses it for shared accounts: the codes stay on the phone of whoever set them up.

What Authy has become

• Mobile only. The Windows, macOS and Linux desktop apps ended on 19 March 2024 (source), and the Chrome extension has not been maintained since 2020 (source).
• One account per person. An Authy account is tied to a phone number; sync is there to get your own codes back on your own devices, and Authy offers no shared vault.
• No export. Authy lets you neither import nor export accounts (source): leaving it means setting up 2FA again on every service.
• July 2024. Twilio stated that phone numbers associated with Authy accounts may have been collected through an unauthenticated endpoint, since secured, and said that the accounts themselves were not compromised (source).

What a team needs instead

In Share Auth, 2FA accounts live in the team’s workspace rather than on a phone, and every authorised member gets the current code from the website, the API, Slack or Discord. A reader receives that code without ever seeing the secret that produces it, so when they leave the team they take no copy with them. The access log shows who got which code, and when.

Your accounts are not locked in either. Each secret’s page shows its setup QR code, which any TOTP app can read. That is exactly what Authy does not allow.

Moving from Authy to Share Auth

With no export, migration happens one account at a time: open the service’s security settings, change authenticator app, scan the new QR code in Share Auth and confirm with the code shown. Start with the accounts the team uses most. The Migration page covers each case.