Cybersecurity · head to head
Authy vs Ory Kratos
Authy
Cybersecurity
Twilio's free authenticator app with encrypted cloud backup, mobile only since the desktop clients were withdrawn in 2024.
- From
- Free
- Rated
- -
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.; Ory Kratos headless means you build every screen, which is significant work compared with a hosted login page
- They diverge on capability: Authy covers Encrypted cloud backup, Ory Kratos covers Headless API.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Authy and Ory Kratos actually diverge.
| Attribute | Authy | Ory Kratos |
|---|---|---|
| Pricing model | free | Open-source self-hosted, with a paid managed network |
| Platforms | Web | Linux, Docker, Kubernetes, Self-hosted |
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Cybersecurity).
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 Ory Kratos
- Headless API
- Self-service flows
- Multi-factor authentication
- Pluggable identity schemas
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 Ory Kratos
- A small team sharing access to a service account where the same tokens must be available on more than one handsetnot Ory Kratos
- Replacing SMS-based codes with TOTP for someone who would abandon two-factor entirely if recovery were difficultnot Ory Kratos
- Consolidating tokens scattered across several apps onto one device list with recognisable names and iconsnot Ory Kratos
Ory Kratos
- Products needing complete control over the look and flow of authenticationnot Authy
- Applications that must not hand user identity data to a third partynot Authy
- Teams building identity as infrastructure across several servicesnot 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.
Ory Kratos
- Headless means you build every screen, which is significant work compared with a hosted login page
- More moving parts than a monolithic IAM: Kratos handles identity, and OAuth2 needs Ory Hydra alongside
- Documentation assumes real familiarity with identity concepts and is not a gentle introduction
- Self-hosting identity carries the security and availability burden that hosted providers absorb
Pricing, plan by plan
Authy
FreeNo published plan breakdown. See the Authy review.
Ory Kratos
Free- Self-hostedFree
- Full identity server
- All flows
- Community support
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 Ory Kratos if
- You need headless api.
- You want to start without paying.
- You work on Linux, Docker, Kubernetes, Self-hosted.
- You also want self-service flows.
Questions people ask
- Is Authy or Ory Kratos better?
- Neither clearly leads. Authy starts at Free and Ory Kratos at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Authy or Ory Kratos?
- Authy starts at Free and Ory Kratos at Free.
- Does Authy or Ory Kratos run on more platforms?
- Authy runs on Web. Ory Kratos runs on Linux, Docker, Kubernetes, Self-hosted.
- 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 Ory Kratos is typically brought in for.
- What can Authy do that Ory Kratos cannot?
- Authy covers Encrypted cloud backup, Multi-device sync, Standard TOTP, Offline code generation. Ory Kratos covers Headless API, Self-service flows, Multi-factor authentication, Pluggable identity schemas.
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.
Ory Kratos: Is Ory Kratos free?
Yes, open source and free to self-host. Ory Network is a paid managed service.
Authy: 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.
Ory Kratos: What does headless mean here?
Kratos provides identity flows as APIs and no user interface. You build the login, registration and recovery screens yourself.
Authy: 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.
Ory Kratos: Does Kratos do OAuth2?
No. Kratos handles user identity; OAuth2 and OpenID Connect provider functionality is Ory Hydra, a separate component.
Authy: 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 Logto
- Authy vs authentik
- Authy vs Clerk
- Authy vs Trivy
- Authy vs HashiCorp Vault
- Authy vs Bitwarden
- Authy vs Frontegg
- Authy vs Infisical
- Authy vs Semgrep
- Authy vs Envysion
- Authy vs Feedzai
- Authy vs HashiCorp Boundary
- Authy vs JumpCloud
- Ory Kratos vs LastPass
- Ory Kratos vs 1Password
- Ory Kratos vs Bitdefender Total Security
- Ory Kratos vs Norton 360
- Ory Kratos vs Google Authenticator
- Ory Kratos vs Cisco Duo
- Ory Kratos vs Entrust Identity as a Service
- Ory Kratos vs RoboForm
- Ory Kratos vs ExpressVPN
- Ory Kratos vs Authelia
- Ory Kratos vs Stytch
- Ory Kratos vs WorkOS
- Ory Kratos vs Splunk Enterprise Security
- Ory Kratos vs Sticky Password
- Ory Kratos vs Surfshark
- Ory Kratos vs Tanium
- Ory Kratos vs Teleport
- Ory Kratos vs Logto
- Ory Kratos vs authentik
- Ory Kratos vs Clerk
- Ory Kratos vs Trivy
- Ory Kratos vs HashiCorp Vault
- Ory Kratos vs Bitwarden
- Ory Kratos vs Frontegg
- Ory Kratos vs Infisical
- Ory Kratos vs Semgrep
- Ory Kratos vs Envysion
- Ory Kratos vs Feedzai
- Ory Kratos vs HashiCorp Boundary
- Ory Kratos vs JumpCloud