The best webhook gateways for receiving webhooks in 2026

A webhook gateway sits between the services that send you webhooks and the code that handles them. For each incoming request it:

1. 1.receives it on a stable URL and answers quickly, so the sender doesn't time out or give up;
2. 2.verifies the signature, so forged or replayed requests never reach your code;
3. 3.stores it, so nothing is lost if your service is down;
4. 4.delivers it to one or more of your endpoints, retrying with backoff when they fail;
5. 5.lets you search and replay past events when something goes wrong;
6. 6.paces delivery so a burst from a provider doesn't flatten your service.

You may not need one if you receive a handful of low-stakes webhooks from one provider, already run a durable queue, and are happy to own signature checks, retries and an audit trail yourself. The case for a gateway grows with the number of providers, the cost of a missed event, and how often someone asks "did that webhook arrive?".

• Verification: which providers are pre-configured, and whether generic schemes such as Standard Webhooks and HMAC are supported.
• Retries: how many attempts, over what window, and whether retries are billed.
• Replay and retention: how long events are kept and how you send them again.
• Billing unit: what's actually counted (an event, a delivery, a message or a licence). This matters more than the headline price.
• Rate limiting and private delivery.
• Agent and MCP support: can an AI agent set up and operate it?
• Self-hosting.

Hookdeck Event Gateway: best for breadth of sources and transformations

Who it's for: teams that integrate with many webhook providers and want to shape and route events before they reach their code.

What stands out. According to Hookdeck, Event Gateway has 800+ pre-configured sources, each setting up verification and authentication for that provider. That's by far the largest list here. Transformations (custom functions that change an event before delivery) are unlimited on every plan. It offers routing and filters, Delivery Groups for per-tenant delivery rates, "customizable retry policies and exponential backoff", bulk pause, cancel and replay, and a Terraform provider (Event Gateway). Its Growth plan lists uptime and latency SLAs, SSO, SAML and SCIM, and metrics export.

Pricing. Developer is free up to 10,000 events with 3-day retention and one user. Team starts at $39 a month with 7-day retention; beyond the 10,000 included events, usage up to 5 million events a month is $3.00 per 100,000, billed in 10,000-event steps of $0.30 (pricing). Hookdeck's pricing FAQ says the price of an event includes all its retries. Growth starts at $499 a month with 30-day retention. An event is an inbound request delivered to a destination, so one request can be zero, one or several events. Requests that produce no event are "discarded": 100,000 a month are included, then $2.50 per million. A static IP is a $100 add-on (pricing).

Agents. Hookdeck's MCP server runs locally through its CLI (hookdeck gateway mcp) over stdio. It starts read-only; adding --allow-write registers the tools that create, change or delete data. Hookdeck also publishes Agent Skills (MCP docs).

Trade-offs. Pricing has several moving parts (events, discarded requests, throughput, add-ons), so model your own traffic on its pricing page. Inbound email isn't listed on the pages we checked.

SolidHooks: best for per-delivery pricing and agent-operated pipelines

Who it's for: teams that want a predictable bill, want an AI agent to set up and run the pipeline, or receive events that don't arrive as HTTP.

What stands out.

• Billing per delivery, retries free. A delivery is one event routed to one connection. Automatic retries and manual retries of one delivery aren't billed, nor are duplicate requests or requests that fail verification. Replays are billed, because they create new deliveries (plans).
• Agent-operated. Every capability is in the REST API with an OpenAPI spec and an llms.txt index. A hosted MCP server at https://api.solidhooks.com/mcp lets Claude, Claude Code, Cursor or VS Code manage sources, destinations, connections and deliveries after a browser sign-in, with nothing to install (MCP). For narrower access, Agent Auth gives an agent its own identity and a human approves each capability (Agent Auth).
• Beyond HTTP. A source can have its own email address and turn each message into a stored, routed event (email ingestion). Connect delivers into a private network through an outbound-only connector, with no inbound ports opened (private delivery).

Verification. Presets for Stripe, GitHub, Linear, Shopify, Paystack, Nuvion, OpenAI, Anthropic and Resend, plus Standard Webhooks, generic HMAC, Basic auth and an API-key header. Timestamped schemes are checked against a window you set, 300 seconds by default (verification).

Pricing. Hobby is free for 10,000 deliveries a month with 3-day retention, and stops accepting at the cap. Launch is $29 a month for 50,000 deliveries with 7-day retention; Scale is $375 a month for 1,000,000 with 30-day retention; both then cost $2.75 per 100,000. Retries: 3 attempts within an hour on Hobby, 8 within 36 hours on paid plans (plans, retries).

Trade-offs. Far fewer presets than Hookdeck. No payload transformations, no Terraform provider, no static IPs, no self-hosted edition, and it doesn't send webhooks to your customers.

Svix Ingest: best if you already send with Svix

Who it's for: teams already using Svix Dispatch to send webhooks who want one vendor for both directions.

What stands out. Svix describes Ingest as its gateway for receiving webhooks, with built-in verification, configurable throttling for traffic spikes, and automatic and manual retries (Svix Ingest).

Pricing. The free plan covers up to 50k messages a month across Dispatch, Stream and Ingest. Basic starts at $20 a month and Professional at $490 a month, each with 50k messages included, then $0.0001 per message. Only attempted messages count; filtered messages and retries are free. Each 64 KiB chunk of payload is billed as one message, so large payloads count more than once (Svix pricing). Prices can change, so check the page again before deciding.

Trade-offs. According to Hookdeck's comparison, Ingest has 30+ pre-configured sources, on Professional and above. That's a competitor's figure, so verify the providers you need with Svix.

Convoy: best if you must self-host

Who it's for: teams whose webhooks have to run inside their own environment.

What stands out. Convoy handles both sending and receiving. The Community edition is open source, self-hosted and "free forever", with incoming and outgoing webhooks, automatic retries and message-broker support. Premium, self-hosted, is $999 a month and adds JavaScript transformations, role-based access control, OpenTelemetry export, endpoint circuit breaking, white-labelling and priority support. Enterprise is priced on request (Convoy pricing).

Cloud. Convoy also runs a managed Cloud. Its FAQ says the Cloud trial lasts 14 days and is limited to one project, one organisation, one user and 100 events a day; the self-hosted Premium trial has unlimited events.

Trade-offs. You run the database, the broker and upgrades yourself. According to Hookdeck's comparison, Convoy ships with 3 pre-configured sources.

Building your own

A minimal version is a public endpoint that verifies the signature, writes the raw request to durable storage, returns 2xx, and hands off to a queue with retries and a dead-letter path. It's very doable. The cost is everything after that: a search UI, replay, per-provider signature quirks, timestamp windows, secret rotation, and being on call for it. Build it if you have one or two providers and spare engineering time; otherwise a gateway is usually cheaper than the time.

People mean three different things by this, and the tools differ on each.

1. An MCP server for managing the gateway. An AI assistant connects over MCP and can list failed deliveries, create sources or replay events. SolidHooks runs this as a hosted remote server with browser sign-in (MCP). Hookdeck's runs locally through its CLI and starts read-only (MCP docs).

2. A bridge that turns webhooks into MCP Events. MCP Events is the draft mechanism ChatGPT uses to subscribe to events from an MCP server. Hookdeck has published an open-source mcp-events-bridge, and Svix has described dedicated subscribe and unsubscribe routes for it (Svix). SolidHooks doesn't send MCP Events. It can receive, verify and store the webhooks, and your own MCP server sends the events; our ChatGPT MCP Events guide shows how.

3. A gateway that delivers events to an agent's endpoint. If your agent runs behind an HTTP endpoint, any gateway here can deliver to it. SolidHooks does this, and with Connect it can deliver to an agent inside a private network.

In short, SolidHooks covers the first and third, not the second.

Say you receive 200,000 webhooks a month, each sent to 2 destinations, and 5% of deliveries fail once and are retried. Payloads are under 64 KiB and nothing is replayed or filtered out. Arithmetic only, from each pricing page on 2 November 2026:

• SolidHooks (Launch): 400,000 deliveries; retries free. 50,000 included, 350,000 at $2.75 per 100,000 = $9.63. $38.63 a month.
• Hookdeck (Team): 400,000 events; retries included. All 400,000 fall in the first usage tier, and Hookdeck's pricing calculator charges $3.00 per started 100,000: 4 × $3.00 = $12.00. $51.00 a month. (Hookdeck's FAQ describes usage as pro-rated in 10,000-event steps beyond the 10,000 included, which would give 39 × $0.30 = $11.70, or $50.70.)
• Svix (Basic): retries free. If each webhook counts as one message: 150,000 over the included 50k at $0.0001 = $15, so $35 a month. If each destination counts separately: 350,000 × $0.0001 = $35, so $55 a month. Svix's pricing page doesn't say which applies to Ingest fan-out, so ask Svix.
• Convoy: no per-event price. Community is $0 plus whatever it costs you to run; Premium is $999 a month whatever the volume.

At this volume the managed options land within about $20 of each other. The gap widens with fan-out, large payloads (Svix), filtered-out traffic (Hookdeck) and replays (SolidHooks).

• Many providers, need transformations or Terraform? Hookdeck.
• Want retries free, an agent to run it, or email as a source? SolidHooks.
• Already sending with Svix? Svix Ingest.
• Data must stay on your own infrastructure? Convoy.
• One provider, low stakes, existing queue? Build it.

For a deeper look at the first two, see SolidHooks vs Hookdeck; for more on leaving Hookdeck, see Hookdeck alternatives.