Cybersecurity · head to head
Authy vs Depot
Authy
Cybersecurity
Twilio's free authenticator app with encrypted cloud backup, mobile only since the desktop clients were withdrawn in 2024.
- From
- Free
- Free plan
- Yes
Depot
Developer Tools
Cloud-based builds and CI runs 55x faster with less cost
- From
- Free
- Free plan
- Yes
The short version
- Each has a real cost: Authy there is no export function for stored TOTP secrets, so moving to a different authenticator means disabling and re-enrolling two-factor authentication on every account individually, which is the reason most users stay rather than a reason anyone should choose it.; Depot developer plan minute limits may be insufficient for active development
- They diverge on capability: Authy covers Encrypted cloud backup, Depot covers Depot CI.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Authy and Depot actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Authy
- Encrypted cloud backup
- Multi-device sync
- Standard TOTP
- Offline code generation
- App lock
- Multi-device toggle
- Token organisation
- Free with no account tier
Only in Depot
- Depot CI
- Container builds
- GitHub Actions runners
- Distributed caching
- Build API
- Depot Registry
- Cross-platform builds
- SSH debugging
What people use each for
The jobs each tool is most often brought in to do.
Authy
- An individual who wants two-factor authentication on personal accounts and needs it to survive losing or replacing a phonenot Depot
- A small team sharing access to a service account where the same tokens must be available on more than one handsetnot Depot
- Replacing SMS-based codes with TOTP for someone who would abandon two-factor entirely if recovery were difficultnot Depot
- Consolidating tokens scattered across several apps onto one device list with recognisable names and iconsnot Depot
Depot
- Accelerating Docker builds for container-based developmentnot Authy
- Replacing GitHub Actions runners with faster infrastructurenot Authy
- Distributing cache across Monorepo buildsnot Authy
- Debugging failed CI builds interactively with SSHnot Authy
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Authy
- There is no export function for stored TOTP secrets, so moving to a different authenticator means disabling and re-enrolling two-factor authentication on every account individually, which is the reason most users stay rather than a reason anyone should choose it.
- The Windows, macOS and Linux desktop applications were discontinued in 2024 and stopped working, so any workflow that depended on copying codes on a computer now requires a phone in hand, and users who held tokens only on a desktop client had to restore from backup or re-enrol.
- The account is keyed to a phone number, so an attacker who takes over that number through a SIM swap can begin the device registration flow, and the only remaining control is the backup password that most users set once and cannot recall.
- In 2024 an unauthenticated Twilio endpoint allowed attackers to confirm which numbers from a supplied list were registered Authy accounts, exposing around 33 million phone numbers, which disclosed no codes but handed phishers a validated list of people known to use two-factor authentication.
- It is a free consumer application inside a company that has already retired the paid Authy developer API it once supported, so it carries no revenue of its own, and users should treat its continued existence as a business decision rather than a roadmap commitment.
Depot
- Developer plan minute limits may be insufficient for active development
- Startup plan at $200/mo is expensive for smaller teams
- Business plan requires custom pricing consultation
- macOS M2 runners not available on Developer plan
Pricing, plan by plan
Authy
FreeNo published plan breakdown. See the Authy review.
Depot
Free- Developer$20/month
- 1 user
- 500 Docker build minutes per month
- 2,000 Depot CI minutes per month
- Startup$200/month
- Unlimited users
- 5,000 Docker build minutes per month
- 20,000 Depot CI minutes per month
- Business$undefined/custom
- Custom pricing
- Unlimited users
- Custom monthly compute
Which should you pick?
Choose Authy if
- You need encrypted cloud backup.
- You want to start without paying.
- You also want multi-device sync.
Choose Depot if
- You need depot ci.
- You want to start without paying.
- You work on Cloud, GitHub, CLI.
- You also want container builds.
Questions people ask
- Is Authy or Depot better?
- Neither clearly leads. Authy starts at Free and Depot at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Authy or Depot?
- Authy starts at Free and Depot at Free.
- Does Authy or Depot run on more platforms?
- Authy runs on Web. Depot runs on Cloud, GitHub, CLI.
- Can I use Authy for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Authy best used for?
- Authy is most often used for an individual who wants two-factor authentication on personal accounts and needs it to survive losing or replacing a phone, a small team sharing access to a service account where the same tokens must be available on more than one handset, replacing sms-based codes with totp for someone who would abandon two-factor entirely if recovery were difficult, consolidating tokens scattered across several apps onto one device list with recognisable names and icons. Of those, an individual who wants two-factor authentication on personal accounts and needs it to survive losing or replacing a phone and a small team sharing access to a service account where the same tokens must be available on more than one handset are not what Depot is typically brought in for.
- What can Authy do that Depot cannot?
- Authy covers Encrypted cloud backup, Multi-device sync, Standard TOTP, Offline code generation. Depot covers Depot CI, Container builds, GitHub Actions runners, Distributed caching.
Answered from the vendors’ own pages
Authy: Is Authy still supported?
The mobile apps for iOS and Android are still available and functional. The desktop applications were withdrawn in 2024 and the Authy developer API has been retired in favour of Twilio Verify, so the surrounding product has been shrinking.
Depot: How much faster are Depot runners compared to GitHub Actions?
Depot runners offer 30% faster CPUs and 10x faster networking than standard GitHub-hosted runners, enabling builds to complete significantly faster.
SourceAuthy: Can I export my tokens?
No. There is no export of the underlying secrets, by design. Migrating to another authenticator means going to each service, disabling two-factor authentication and setting it up again with the new app.
Depot: What is included in the Developer plan?
Developer plan ($20/month) includes 500 Docker build minutes, 2,000 Depot CI minutes, 2,000 GitHub Actions minutes, 25 GB storage, unlimited concurrency, and community support.
SourceAuthy: What happened to the desktop app?
Twilio announced its discontinuation in March 2024 and the applications stopped working later that year. There is no replacement desktop client; the mobile apps are the product now.
Depot: Can I use Depot with my own AWS account?
Yes, Depot Managed allows deployment within customer AWS accounts. This is available to interested customers; contact sales for details.
SourceAuthy: Is multi-device sync safe to leave on?
It is the feature most worth understanding. Leaving new device registration enabled means anyone who controls your phone number can attempt to add a device. The usual advice is to turn the multi-device setting off once your devices are registered and turn it on only when you need to add one.
Authy: What if I lose my phone and forget the backup password?
The secrets are encrypted with that password and Twilio does not hold it, so they cannot be recovered. You would fall back to each individual service's account recovery process, which is exactly the situation the backup was meant to avoid.
Related pages
Other head to heads
- Authy vs LastPass
- Authy vs 1Password
- Authy vs Bitdefender Total Security
- Authy vs Norton 360
- Authy vs Google Authenticator
- Authy vs Cisco Duo
- Authy vs Entrust Identity as a Service
- Authy vs RoboForm
- Authy vs ExpressVPN
- Authy vs Authelia
- Authy vs Stytch
- Authy vs WorkOS
- Authy vs Splunk Enterprise Security
- Authy vs Sticky Password
- Authy vs Surfshark
- Authy vs Tanium
- Authy vs Teleport
- Authy vs WarpBuild
- Authy vs Blacksmith
- Authy vs Nixpacks
- Authy vs Buildkite
- Authy vs GitLab CI/CD
- Authy vs Namespace
- Authy vs Earthly
- Authy vs Nx Cloud
- Authy vs Dagger
- Authy vs Garden
- Authy vs Ansible
- Authy vs ConfigCat
- Authy vs Avo
- Authy vs Azure DevOps
- Authy vs Backstage
- Authy vs Bitbucket
- Authy vs Claude Code
- Authy vs Cloud Native Buildpacks
- Depot vs LastPass
- Depot vs 1Password
- Depot vs Bitdefender Total Security
- Depot vs Norton 360
- Depot vs Google Authenticator
- Depot vs Cisco Duo
- Depot vs Entrust Identity as a Service
- Depot vs RoboForm
- Depot vs ExpressVPN
- Depot vs Authelia
- Depot vs Stytch
- Depot vs WorkOS
- Depot vs Splunk Enterprise Security
- Depot vs Sticky Password
- Depot vs Surfshark
- Depot vs Tanium
- Depot vs Teleport
- Depot vs WarpBuild
- Depot vs Blacksmith
- Depot vs Nixpacks
- Depot vs Buildkite
- Depot vs GitLab CI/CD
- Depot vs Namespace
- Depot vs Earthly
- Depot vs Nx Cloud
- Depot vs Dagger
- Depot vs Garden
- Depot vs Ansible
- Depot vs ConfigCat
- Depot vs Avo
- Depot vs Azure DevOps
- Depot vs Backstage
- Depot vs Bitbucket
- Depot vs Claude Code
- Depot vs Cloud Native Buildpacks