Softwr

Developer Tools · head to head

Hookdeck vs Nango

Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Rated
-
Full reviewWebsite
Nango logo

Nango

Automation Integration

Open source unified API and OAuth infrastructure for product integrations, licensed under Elastic License 2.0

From
Free
Rated
-
Full reviewWebsite

The short version

  • 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.; Nango the licence is Elastic License 2.0, which is source available rather than OSI open source, and it forbids offering Nango to third parties as a managed service, so anyone planning to resell or embed it in a platform for their own customers has a genuine legal problem.
  • They diverge on capability: Hookdeck covers Ingest and persist, Nango covers Managed OAuth.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Hookdeck and Nango actually diverge.

Attributes where Hookdeck and Nango differ
AttributeHookdeckNango
Pricing modelPer month by delivered event countPer connection per month
PlatformsWeb, Linux, macOS, WindowsWeb, Linux, Docker
CategoryDeveloper ToolsAutomation Integration

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 Hookdeck

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

Only in Nango

  • Managed OAuth
  • Pre-built integrations
  • Custom syncs and actions
  • Incremental sync
  • Rate limit and retry handling
  • Webhooks
  • Self-hosting
  • Unified models

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 Nango
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Nango
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Nango
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Nango

Nango

  • A SaaS product that needs to ship twenty customer-facing integrations without hiring a team to maintain OAuth and token refresh for eachnot Hookdeck
  • A team that needs a niche or internal API integrated, which closed unified API vendors will not build for themnot Hookdeck
  • A company with data residency or security constraints that must self-host the integration layer rather than send customer tokens to a vendornot Hookdeck
  • An engineering team replacing a homegrown integration service whose main cost is silent token expiry and rate limit failures in productionnot 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.

Nango

  • The licence is Elastic License 2.0, which is source available rather than OSI open source, and it forbids offering Nango to third parties as a managed service, so anyone planning to resell or embed it in a platform for their own customers has a genuine legal problem.
  • Pricing is per connection where a connection is one authorised end-user account, so cost scales linearly with your customer base and a product where each user links several services multiplies quickly beyond what a headline plan price suggests.
  • Pre-built integrations vary in depth, and a connection that exists is not the same as a connection that covers the endpoints and objects your feature needs, so each one must be verified before it is designed into a roadmap.
  • Custom syncs are written in TypeScript and run in Nango model, which means integration logic lives in a vendor runtime and migrating away later requires rewriting it rather than lifting it out.
  • Self-hosting removes the vendor from the data path but transfers operational responsibility for a component that holds customer OAuth tokens, and few teams appreciate the security burden that comes with running that themselves.

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

Nango

Free
  • FreeFree
    • 10 connections
    • Pre-built integrations
    • Managed OAuth
  • Starter$50/month
    • 20 connections included
    • 1 USD per additional connection
    • Custom syncs and actions
  • Growth$500/month
    • 100 connections included
    • 1 USD per additional connection
    • Higher limits
  • Enterprise$undefined/month
    • Quoted
    • Custom connection volumes
    • Security review and SLA

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.
Hookdeck review

Choose Nango if

  • You need managed oauth.
  • You want to start without paying.
  • You work on Web, Linux, Docker.
  • You also want pre-built integrations.
Nango review

Questions people ask

Is Hookdeck or Nango better?
Neither clearly leads. Hookdeck starts at Free and Nango at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hookdeck or Nango?
Hookdeck starts at Free and Nango at Free.
Does Hookdeck or Nango run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. Nango runs on Web, Linux, Docker.
Can I use Hookdeck for free?
Both have a free tier, so you can try either at no cost before committing.
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 Nango is typically brought in for.
What can Hookdeck do that Nango cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. Nango covers Managed OAuth, Pre-built integrations, Custom syncs and actions, Incremental sync.

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.

Nango: Is Nango open source?

It is source available under Elastic License 2.0. You can read, modify and self-host it, but you cannot offer it to third parties as a managed service. That is not the same as an OSI approved open source licence.

Hookdeck: How is usage counted?

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

Nango: How is it priced?

Per connection per month, where a connection is one authorised end-user account. Free to 10 connections, 50 dollars a month for Starter with 20, 500 for Growth with 100, and one dollar per additional connection.

Hookdeck: Can I replay a failed webhook?

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

Nango: Can we integrate an API Nango does not support?

Yes. Custom syncs and actions in TypeScript cover any API including internal ones, which is the main advantage over closed unified API products.

Hookdeck: Does it work for outbound webhooks too?

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

Nango: Can we self-host it?

Yes, under the Elastic License 2.0 terms, which permit self-hosting for your own use but not resale as a service.

Share

Related pages

More on Hookdeck

More on Nango

Keep looking

Other head to heads