Why they built it
The founders saw internet services relying on passwords alone because building two-factor enrollment, delivery, recovery and fraud controls was too much work for ordinary product teams. They thought a developer API plus an authenticator app that generated time-based codes offline and handled encrypted backups could remove that work and make stronger authentication practical.
How it ended
Authy did not fail as a standalone startup; Twilio acquired it in February 2015 for $3 million in cash and $3.1 million in preferred stock after roughly 6,000 sites had adopted it. Twilio bought it because Authy cut authentication integration from months to days, with CEO Jeff Lawson saying Authy had already built the solution Twilio would have built.
What went wrong
Most important first.
- 1
Phone-number recovery concentrated risk Technology
The phone-number bridge enabled encrypted backup and sync across devices, but attackers registered devices on 93 accounts during Twilio's 2022 social-engineering breach and a July 2024 unauthenticated endpoint exposed Authy account phone numbers.
- 2
TOTP-centered model superseded by passkeys Technology
Authy improved a TOTP and SMS world, but passkeys using public-key credentials now resist phishing better than shared secrets, with AWS IAM adding passkeys as a second factor in June 2024, leaving TOTP as compatibility.
What could be different today
- Passkeys using public-key credentials are now mainstream phishing-resistant authentication, with AWS IAM adding passkeys as a second factor in June 2024, so a rebuild would treat TOTP as a compatibility layer.
- Authy desktop apps reached end of life in March 2024, while teams now manage a mixed estate of passkeys, legacy TOTP and recovery codes across devices, platform keychains and authenticator apps.
- Twilio added QR enrollment that kept phone and email data from the relying website, providing a privacy-preserving enrollment pattern a rebuild could use from the start.
