Twilio's Authy product offerings are built on top of the Twilio messaging stack, and offer pre-built verification solutions for Two-Factor Authentication or one-time phone verification. Because they are pre-built, there are some limitations compared to the full flexibility of building your own solution in Twilio messaging.
|Authy handles the from number
|You handle the from number
|Authy will pay for the from number, and may use a variety of local and international long codes, short codes or alphanumerics for greater deliverability. If you need to designate a specific from number, you should build your own solution in Twilio.
|Authy API key is unique to Authy API endpoints
|Twilio auth token works across other Twilio products.
|The Authy API key needs the same safe handling as the Twilio auth token and can be rotated as needed.
|Authy requests will be billed to your project
|Twilio allows billing usage by subaccount
|Authy customers will need to use separate Authy applications for each contracted customer if billing needs to be tracked separately in the Twilio project.
|Authy administrators should be added as collaborators to the Authy Dashboard on a per-application basis
|Twilio project user management does not apply to Authy
|Authy Dashboard is in the process of integration with Twilio Console, and the old site dashboard.authy.com is now in code freeze as migration is underway.
|Authy does not yet support outbound message/call logging or error logging
|Authy will be adding logging in the Twilio console and may add reporting API endpoints in future. For now, errors and usage must be tracked by API response from Authy to your server.
|Authy helper libraries are stand alone
|Multiple Twilio products supported in each helper library
|Be sure to download the Authy helper library separate from the Twilio helper libraries.