Softwr

Cybersecurity · head to head

Authy vs Soketi

Authy logo

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
Soketi logo

Soketi

Developer Tools

Self-hosted, Pusher-compatible WebSockets server with a stalled maintenance record

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.; Soketi maintenance has effectively stalled: the maintainer has said time is severely limited, releases are infrequent, and the community has been discussing whether the project is abandoned, which means security fixes may not arrive.
  • They diverge on capability: Authy covers Encrypted cloud backup, Soketi covers Pusher protocol compatibility.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Authy and Soketi actually diverge.

Attributes where Authy and Soketi differ
AttributeAuthySoketi
Pricing modelfreeOpen source, no licence fee
PlatformsWebLinux, macOS, Windows
CategoryCybersecurityDeveloper Tools

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 Soketi

  • Pusher protocol compatibility
  • Presence and private channels
  • Horizontal scaling
  • App management backends
  • Webhooks
  • Prometheus metrics

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 Soketi
  • A small team sharing access to a service account where the same tokens must be available on more than one handsetnot Soketi
  • Replacing SMS-based codes with TOTP for someone who would abandon two-factor entirely if recovery were difficultnot Soketi
  • Consolidating tokens scattered across several apps onto one device list with recognisable names and iconsnot Soketi

Soketi

  • A Laravel application that already uses Echo and wants to stop paying a hosted realtime providernot Authy
  • Realtime notifications or presence indicators where data must not leave your own infrastructure for compliance reasonsnot Authy
  • A local or CI environment that needs a Pusher-compatible server without hitting a paid accountnot Authy
  • A high-connection-count application where hosted per-connection pricing has become the largest line in the infrastructure billnot 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.

Soketi

  • Maintenance has effectively stalled: the maintainer has said time is severely limited, releases are infrequent, and the community has been discussing whether the project is abandoned, which means security fixes may not arrive.
  • Dependency drift on Node and uWebSockets.js will eventually force you to fork or migrate, and that cost is unbudgeted at the point you adopt it.
  • There is no commercial support to buy, so a production incident at three in the morning is entirely your problem with no escalation path.
  • Scaling beyond a single node needs Redis and careful configuration, and getting presence channels correct across nodes is a genuine source of subtle bugs.
  • It implements the Pusher protocol rather than tracking it, so any protocol feature Pusher adds later will not appear, and the compatibility guarantee slowly decays.

Pricing, plan by plan

Authy

Free

No published plan breakdown. See the Authy review.

Soketi

Free
  • SoketiFree
    • MIT licensed
    • Unlimited connections subject to your own hardware
    • No vendor billing

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 Soketi if

  • You need pusher protocol compatibility.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want presence and private channels.

Questions people ask

Is Authy or Soketi better?
Neither clearly leads. Authy starts at Free and Soketi at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Authy or Soketi?
Authy starts at Free and Soketi at Free.
Does Authy or Soketi run on more platforms?
Authy runs on Web. Soketi runs on Linux, macOS, Windows.
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 Soketi is typically brought in for.
What can Authy do that Soketi cannot?
Authy covers Encrypted cloud backup, Multi-device sync, Standard TOTP, Offline code generation. Soketi covers Pusher protocol compatibility, Presence and private channels, Horizontal scaling, App management backends.

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.

Soketi: Is Soketi still maintained?

Barely. The maintainer has stated that available time is very limited and releases have been sparse; treat it as community-maintained.

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.

Soketi: Do I need to change my client code?

No. Pusher client SDKs and Laravel Echo work by changing the host, port and credentials.

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.

Soketi: What does it cost?

Nothing in licence fees. It is MIT licensed; you pay for the server it runs on.

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.

Soketi: What are people moving to?

Laravel Reverb for Laravel applications, and Sockudo, a Rust reimplementation, for others.

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.

Share

Related pages

Other head to heads