Softwr

Developer Tools · head to head

Hookdeck vs ngrok

Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Free plan
Yes
ngrok logo

ngrok

Networking

Reverse tunnel service that gives a local or private service a public URL without opening a firewall

From
Free
Free plan
Yes

The short version

  • ngrok is free; Hookdeck starts at $39/mo.
  • Only Hookdeck lists ingest and persist; only ngrok lists outbound agent tunnels.
  • Where Hookdeck falls short: pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Where ngrok falls short: bandwidth is metered on paid tiers, so a workload that quietly grows into serving real traffic produces overage rather than a flat bill.
  • Prices and features on this page were last checked on 20 November 2026.

How do Hookdeck and ngrok differ?

Hookdeck and ngrok differ on pricing model, platforms and category (Developer Tools against Networking). Only the attributes on which Hookdeck and ngrok actually diverge.

Attributes where Hookdeck and ngrok differ
AttributeHookdeckngrok
Pricing modelPer month by delivered event countPer user per month
PlatformsWeb, Linux, macOS, WindowsLinux, macOS, Windows, Self-hosted
CategoryDeveloper ToolsNetworking

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 6 appear only for Hookdeck and 6 only for ngrok. 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 ngrok

  • Outbound agent tunnels
  • Static domains
  • Traffic policy
  • Request inspection
  • Kubernetes ingress
  • TCP and TLS endpoints

What is each one used for?

ngrok is most often brought in for giving a partner a temporary authenticated endpoint into an internal API. 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 ngrok
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot ngrok
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot ngrok
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot ngrok

ngrok

  • Receiving webhooks from a payment or messaging provider on a laptop during developmentnot Hookdeck
  • Demonstrating a work in progress application to someone outside the network without deploying itnot Hookdeck
  • Publishing a service inside a private network or Kubernetes cluster without a public load balancernot Hookdeck
  • Giving a partner a temporary authenticated endpoint into an internal APInot Hookdeck

Where do Hookdeck and ngrok fall 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

ngrok

  • Free HTTP endpoints show a browser interstitial before the page loads, which breaks first impressions in demos and confuses anyone you send the link to
  • All traffic passes through ngrok infrastructure, so you inherit its latency and an ngrok incident takes every published endpoint down at once with no local failover
  • Pricing is per user seat plus allowances, so a platform team publishing many endpoints ends up buying seats for people who never open the dashboard
  • Bandwidth is metered on paid tiers, so a workload that quietly grows into serving real traffic produces overage rather than a flat bill
  • Traffic policy configuration is specific to ngrok, so the authentication and routing logic you accumulate at the edge has to be rebuilt if you later move to a conventional ingress

How much do Hookdeck and ngrok cost?

Hookdeck has a free plan, with paid plans from $39/mo; ngrok is free to use. Plan by plan below, from each vendor's own pricing page.

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/mo
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/mo
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • EnterpriseOn request
    • Negotiated event volume
    • Custom retention
    • Dedicated support

ngrok

Free
  • FreeFree
    • One static domain
    • HTTP endpoints with a browser interstitial
    • Limited simultaneous connections
  • PersonalOn request
    • Removes the interstitial warning page
    • Additional reserved domains
    • TCP endpoints
  • ProOn request
    • Per user billing with team accounts
    • Traffic policy rules and edge authentication
    • Higher bandwidth allowances
  • EnterpriseOn request
    • Custom terms and volume pricing
    • Dedicated capacity options
    • Compliance and audit requirements

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

  • You need outbound agent tunnels.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Self-hosted.
  • You also want static domains.

Questions people ask

Is Hookdeck or ngrok better?
Neither clearly leads. Hookdeck starts at Free and ngrok at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Hookdeck or ngrok?
Hookdeck starts at Free and ngrok at Free.
Does Hookdeck or ngrok run on more platforms?
Hookdeck runs on Web, Linux, macOS, Windows. ngrok runs on Linux, macOS, Windows, Self-hosted.
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 ngrok is typically brought in for.
What can Hookdeck do that ngrok cannot?
Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations. ngrok covers Outbound agent tunnels, Static domains, Traffic policy, Request inspection.

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.

ngrok: Can I use it in production?

It is sold for that now, with static domains, policy rules and a Kubernetes operator. The question is whether you accept a third party on the traffic path for every request.

Hookdeck: How is usage counted?

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

ngrok: Why does my free URL show a warning page?

Free HTTP endpoints carry an interstitial. Removing it requires a paid plan, and it is the most common reason people upgrade.

Hookdeck: Can I replay a failed webhook?

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

ngrok: Does it work for SSH or a database?

Yes through TCP endpoints, which are a paid feature.

Hookdeck: Does it work for outbound webhooks too?

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

ngrok: What is the self hosted alternative?

A reverse proxy on a server you own with a tunnel back to the service, or one of the self hosted tunnel projects. All of them cost more setup time than the thing they replace.

Share

Related pages

Other head to heads