Comparison · Verified October 31, 2026

Hooks vs Convoy

Short answer: Convoy is an open-source-friendly webhook gateway with cloud and self-hosted options; Hooks is a hosted gateway focused on turning webhooks into AI agent tasks.

Both give every endpoint a stable ingest URL, verify signatures, and retry deliveries. Choose Convoy when you must self-host or want a multi-project gateway with broad protocol support; choose Hooks when the destination is an AI agent and you want per-target templates, filters, and run tracking without running infrastructure.

Start for free Read the docs

Hooks vs Convoy: side by side

Capability	Hooks	Convoy
Sources	GitHub, Stripe, Slack, Linear, generic HMAC-SHA256 (Sentry planned)	Broad webhook sources via endpoints, portals, and subscriptions
AI agent targets	First-class: Grok Bot, T3 Code, Paseo (run id recorded), Slack	Generic HTTP endpoints; agent task APIs wired manually per subscription
Payload templates	Declarative field paths, defaults, and filters per destination	Transformations and fan-out configuration per subscription
Filtering	Per-destination filter rules evaluated before delivery	Subscription filters and event types
Retries	Per-target retry schedule with replayable delivery log	Configurable retry logic with dead-letter handling
Delivery log	Event log with per-delivery attempts, rendered request, target response, replay	Dashboard and API with event deliveries and replays
Pricing	Hobby free (10,000 events/mo), Pro $1/mo billed annually ($10/yr, 250,000 events/mo), Scale custom	Convoy Cloud metered plans plus a self-hosted option you run yourself
Self-hosting	Hosted service only	Self-hostable alongside Convoy Cloud

Webhook gateway with Convoy Cloud and self-hosted deploys.

Choose Hooks when

AI agent delivery is the job: task-shaped payloads, per-agent templates, and run ids in the log.
You want zero infrastructure — no clusters, queues, or upgrades to operate.
Your team prefers one REST API for endpoints, destinations, retries, and replay.

Choose Convoy when

Policy requires running the gateway inside your own VPC or data residency boundary.
You need multi-project routing, portals, or protocol options beyond HTTPS agent targets.
You already run Convoy self-hosted and want receiving and sending in one control plane.

Where Hooks falls short

No tool fits every team. These are the honest gaps in this matchup — if one is a deal-breaker, the other option is the right call.

No self-hosted option; regulated or air-gapped teams cannot run Hooks inside their own network.
Source catalog is smaller than Convoy's, and Sentry support is still planned.
No JS transformation sandbox; complex reshaping beyond declarative templates is not supported yet.

Frequently asked questions

Can I self-host Hooks like Convoy?

No. Hooks is hosted-only on Cloudflare. Teams that must self-host should use Convoy's self-hosted deploy or another open-source gateway, and can still evaluate Hooks for side projects.

Which handles AI agent targets better?

Hooks: agent targets (Grok Bot, T3 Code, Paseo) are built in with task-shaped templates, per-target filters and retries, and recorded run ids. Convoy reaches the same APIs as generic HTTP endpoints, which means hand-writing the task mapping yourself.

How does pricing differ?

Hooks charges flat per-workspace tiers (Hobby free, Pro $1/mo billed annually, Scale custom). Convoy Cloud meters usage and self-hosting costs whatever you run. High-volume teams should model both against real event counts.

Do both support replay?

Yes. Hooks replays events to their destinations from the delivery log; Convoy supports event replay and export for backfills. Both keep the raw payload so replays use the original event.

Sources

Every fact above traces to one of these pages, last checked on October 31, 2026.

Convoyhttps://www.convoy.sh
Convoy comparisonshttps://www.convoy.sh/vs
Svix Dispatch vs Convoyhttps://www.svix.com/vs/svix-dispatch-vs-convoy/
Hooks documentationhttps://hooks.events/docs
Hooks pricinghttps://hooks.events/pricing

Keep comparing

Hooks vs HookdeckHookdeck Event Gateway is general-purpose webhook infrastructure; Hooks is a narrower webhook gateway that turns received events into AI agent tasks.Hooks vs Svix IngestSvix Ingest receives webhooks into the Svix sending platform; Hooks receives webhooks and routes them to AI agent and HTTP targets with filters and templates.Hooks vs DIY Cloudflare WorkerA DIY Cloudflare Worker costs pennies per million requests but you own retries, logs, replay, and secret rotation; Hooks bundles all of that for a flat per-workspace price.webhook.site alternativewebhook.site gives you instant throwaway URLs to inspect requests; Hooks gives every endpoint a stable URL that verifies, filters, reshapes, and forwards events to AI agents.smee.io alternativesmee.io proxies webhook payloads to your localhost over server-sent events; Hooks receives the same webhooks and routes them to AI agents and HTTP targets with retries.ngrok alternativengrok tunnels the public internet to your localhost; Hooks replaces the tunnel-plus-handler stack with hosted ingress that verifies and routes to AI agents.