Softwr

Developer Tools · head to head

Hookdeck vs IDnow

Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Free plan
Yes
IDnow logo

IDnow

Cybersecurity

Identity verification and qualified electronic signature for regulated European markets

From
On request
Free plan
No

The short version

  • Only Hookdeck has a free tier, so it costs nothing to try first.
  • Each has a real cost: Hookdeck pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.; IDnow agent-led video identification costs several times an automated check and depends on agent availability, so peak-time queues push abandonment up at exactly the moment conversion matters.
  • They diverge on capability: Hookdeck covers Ingest and persist, IDnow covers VideoIdent.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Hookdeck and IDnow actually diverge.

Attributes where Hookdeck and IDnow differ
AttributeHookdeckIDnow
Starting priceFreeOn request
Pricing modelPer month by delivered event countquote
Free tierYesNo
PlatformsWeb, Linux, macOS, WindowsWeb, iOS, Android, API
CategoryDeveloper ToolsCybersecurity

Identical on both: 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 Hookdeck

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

Only in IDnow

  • VideoIdent
  • AutoIdent
  • eSign
  • eID and NFC
  • Bank identification
  • EU data processing

What people use each for

The jobs each tool is most often brought in to do.

Hookdeck

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

IDnow

  • A German bank opening regulated accounts where BaFin requires a recognised identification methodnot Hookdeck
  • An insurer needing a qualified electronic signature that will survive challenge in a European courtnot Hookdeck
  • A telecom operator meeting national SIM registration identity rules across several EU statesnot Hookdeck
  • A lender wanting automated checks for low-risk applicants and video identification only for high-value casesnot Hookdeck

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

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.

IDnow

  • Agent-led video identification costs several times an automated check and depends on agent availability, so peak-time queues push abandonment up at exactly the moment conversion matters.
  • Pricing is quoted with an annual volume commitment, so the accreditation advantage comes with a floor you pay whether or not you use it.
  • The product is optimised for European regulatory regimes, so buyers verifying users in North America, Asia or Africa will find coverage and cost less competitive than global specialists.
  • Qualified electronic signature is a separate licence from identity verification, which surprises buyers who assumed the accredited identity check made the signature capability included.
  • Integration for the regulated flows is heavier than a simple SDK drop-in because the compliant journey, including consent and recording requirements, constrains the user experience you can build.

Pricing, plan by plan

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

IDnow

On request
  • IDnow Platform$undefined/year
    • Per-identification pricing that differs sharply between automated and agent-led methods
    • Annual volume commitment typically required
    • Qualified electronic signature licensed separately

Which should you pick?

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.

Choose IDnow if

  • You need videoident.
  • You work on Web, iOS, Android, API.
  • You also want autoident.

Questions people ask

Is Hookdeck or IDnow better?
Neither clearly leads. Hookdeck starts at Free and IDnow at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hookdeck or IDnow?
Hookdeck has a free tier; the other does not. Paid plans start at Free for Hookdeck and On request for IDnow.
Does Hookdeck or IDnow run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. IDnow runs on Web, iOS, Android, API.
Can I use Hookdeck for free?
Yes. Hookdeck has a free tier, so you can try it without paying. IDnow starts at On request.
What is Hookdeck best used for?
Hookdeck is most often used for a payments integration where losing a stripe event during a deploy causes an order to go unfulfilled, fanning one provider webhook out to several internal services without each subscribing separately, debugging a partner integration by replaying the exact failing payload after shipping a fix, receiving production-shaped webhooks on a developer laptop without running a public tunnel. Of those, a payments integration where losing a stripe event during a deploy causes an order to go unfulfilled and fanning one provider webhook out to several internal services without each subscribing separately are not what IDnow is typically brought in for.
What can Hookdeck do that IDnow cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. IDnow covers VideoIdent, AutoIdent, eSign, eID and NFC.

Answered from the vendors’ own pages

Hookdeck: Is there a free plan?

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

IDnow: Why choose it over a cheaper automated vendor?

Because in some European regimes the cheaper vendor is not legally permitted for the transaction. This is an eligibility question, not a quality one.

Hookdeck: How is usage counted?

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

IDnow: Is the electronic signature included?

No. Qualified electronic signature under eIDAS is licensed separately from identity verification.

Hookdeck: Can I replay a failed webhook?

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

IDnow: Where is the data processed?

In European data centres, which is a requirement rather than a preference for many of its regulated customers.

Hookdeck: Does it work for outbound webhooks too?

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

Share

Related pages

Other head to heads