Softwr

Cybersecurity · head to head

Authy vs Hookdeck

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

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

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.; Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • They diverge on capability: Authy covers Encrypted cloud backup, Hookdeck covers Ingest and persist.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Authy and Hookdeck actually diverge.

Attributes where Authy and Hookdeck differ
AttributeAuthyHookdeck
Pricing modelfreePer month by delivered event count
PlatformsWebWeb, Linux, 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 Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

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

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Authy
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Authy
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Authy
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot 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.

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone.
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once.
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead.
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate.

Pricing, plan by plan

Authy

Free

No published plan breakdown. See the Authy review.

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/month
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/month
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • Enterprise$undefined/year
    • Negotiated event volume
    • Custom retention
    • Dedicated 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 Hookdeck if

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.

Questions people ask

Is Authy or Hookdeck better?
Neither clearly leads. Authy starts at Free and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Authy or Hookdeck?
Authy starts at Free and Hookdeck at Free.
Does Authy or Hookdeck run on more platforms?
Authy runs on Web. Hookdeck runs on Web, 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 Hookdeck is typically brought in for.
What can Authy do that Hookdeck cannot?
Authy covers Encrypted cloud backup, Multi-device sync, Standard TOTP, Offline code generation. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

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.

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

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.

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

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.

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

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.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

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