Softwr

APIs · head to head

Convoy vs Hookdeck

Convoy logo

Convoy

APIs

Open source webhooks gateway you self-host, handling both sending and receiving

From
Free
Rated
-
Full reviewWebsite
Hookdeck logo

Hookdeck

Developer Tools

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

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Convoy the default deployment is self-hosted, so you operate Convoy plus Postgres and Redis and carry the on-call burden for the system that delivers your customers' events.; 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: Convoy covers Inbound and outbound, Hookdeck covers Ingest and persist.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Convoy and Hookdeck actually diverge.

Attributes where Convoy and Hookdeck differ
AttributeConvoyHookdeck
Pricing modelPer month, flat rate regardless of volumePer month by delivered event count
PlatformsLinux, Docker, Kubernetes, CloudWeb, Linux, macOS, Windows
CategoryAPIsDeveloper 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 Convoy

  • Inbound and outbound
  • Broker-driven ingestion
  • Payload transformation
  • Portal links
  • Circuit breaking
  • Retry policies
  • OpenTelemetry export
  • Role-based access control

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.

Convoy

  • A fintech that cannot route customer webhook traffic through a third-party SaaS for compliance reasonsnot Hookdeck
  • A high-volume platform for which per-message webhook pricing costs more than the flat premium licencenot Hookdeck
  • A team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gatewaynot Hookdeck
  • An engineering group that wants webhook delivery driven directly from an existing Kafka or SQS topicnot Hookdeck

Hookdeck

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

Where each one falls short

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

Convoy

  • The default deployment is self-hosted, so you operate Convoy plus Postgres and Redis and carry the on-call burden for the system that delivers your customers' events.
  • Frain Technologies is a small startup, and putting customer-facing delivery infrastructure on it means accepting real vendor continuity risk on a component that is hard to swap out quickly.
  • The premium tier at a flat 999 US dollars a month is poor value below substantial volume, while the community edition omits the portal, transformations and RBAC that most production deployments end up wanting.
  • The hosted cloud trial is capped at one project and 100 events a day, which is too small to properly evaluate the service before committing.
  • Documentation and the third-party ecosystem are thinner than the established webhook services, so unusual configurations often mean reading the Go source.

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

Convoy

Free
  • CommunityFree
    • Self-hosted open source gateway
    • Inbound and outbound webhooks
    • Automatic retries and message broker support
  • Premium$999/month
    • Flat rate irrespective of message volume
    • Portal links and payload transformation
    • RBAC, circuit breaking and white labelling
  • Enterprise$undefined/year
    • SAML SSO
    • Dedicated support with SLA
    • On-premises deployment assistance
  • Cloud$undefined/month
    • Hosted by Convoy
    • 14 day trial limited to one project and 100 events a day
    • Usage-based tiers above the trial

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

  • You need inbound and outbound.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Cloud.
  • You also want broker-driven ingestion.
Convoy review

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

Questions people ask

Is Convoy or Hookdeck better?
Neither clearly leads. Convoy 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, Convoy or Hookdeck?
Convoy starts at Free and Hookdeck at Free.
Does Convoy or Hookdeck run on more platforms?
Convoy runs on Linux, Docker, Kubernetes, Cloud. Hookdeck runs on Web, Linux, macOS, Windows.
Can I use Convoy for free?
Both have a free tier, so you can try either at no cost before committing.
What is Convoy best used for?
Convoy is most often used for a fintech that cannot route customer webhook traffic through a third-party saas for compliance reasons, a high-volume platform for which per-message webhook pricing costs more than the flat premium licence, a team that also receives webhooks from many providers and wants ingestion, verification and deduplication in the same gateway, an engineering group that wants webhook delivery driven directly from an existing kafka or sqs topic. Of those, a fintech that cannot route customer webhook traffic through a third-party saas for compliance reasons and a high-volume platform for which per-message webhook pricing costs more than the flat premium licence are not what Hookdeck is typically brought in for.
What can Convoy do that Hookdeck cannot?
Convoy covers Inbound and outbound, Broker-driven ingestion, Payload transformation, Portal links. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

Answered from the vendors’ own pages

Convoy: Is Convoy really open source?

Yes, the community edition is open source and self-hostable, covering both inbound and outbound webhooks with retries.

Hookdeck: Is there a free plan?

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

Convoy: What does premium cost?

A flat 999 US dollars a month, self-hosted, regardless of message volume.

Hookdeck: How is usage counted?

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

Convoy: Does it receive webhooks as well as send them?

Yes, inbound ingestion with verification and deduplication is a first-class feature, unlike most webhook services.

Hookdeck: Can I replay a failed webhook?

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

Convoy: Do I have to self-host?

No, there is a hosted cloud, but the trial is capped at 100 events a day and self-hosting is the primary model.

Hookdeck: Does it work for outbound webhooks too?

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

Share

Related pages

More on Convoy

More on Hookdeck

Keep looking

Other head to heads