How Hookway compares
Compare Hookway, Hookdeck Event Gateway and Convoy across webhook delivery, API routing and MCP tools. Hookway runs in your infrastructure and sends events directly to queues, streams, databases, and object storage. It also handles synchronous HTTP requests, reverse proxies to APIs, and exposes configurable MCP endpoints. Its optional replay service lets you inspect and retry missed deliveries through a scoped operations console or API. Each claim links to its supporting docs.
Products in this comparison
Hookway, Hookdeck Event Gateway and Convoy overlap on webhooks, but serve different workflows. Outpost is covered separately below.
Hookway
This product
Self-hosted webhook and MCP gateway. Core is one binary configured in YAML; replay and the frontend are optional separate services.
hook_way repositoryHookdeck Event Gateway
Managed inbound event gateway: ingest, queue, transform, and deliver to HTTP (plus CLI and Mock API destinations).
Hookdeck Destinations docsConvoy
Open-source webhook gateway for ingesting and delivering webhooks, with HTTP endpoints as the delivery target.
Convoy introductionFeature and integration matrix
Baseline checked 2026-10-31; newer checks are dated on their rows. Each cell links to its supporting documentation. Delivery, storage and MCP tool boundaries are explained where they matter.
Scroll sideways to read each product's column.
| Capability | Hookway | Hookdeck Event Gateway | Convoy |
|---|---|---|---|
Deployment model | Yes Self-hosted static binary / container you run Documentation | Yes Managed SaaS Event Gateway Documentation | Yes Self-hosted API/workers with PostgreSQL and Redis, or Convoy Cloud Documentation |
Primary config surface | Yes YAML flows + optional visual builder export Documentation | Yes Dashboard, API, Terraform Documentation | Yes Dashboard and API Documentation |
MCP tools Hookway exposes selected APIs as tools; Hookdeck provides gateway administration tools. Checked October 31, 2026. Not documented means the reviewed docs do not establish this capability. | Yes Multiple configurable HTTP endpoints with independent catalogues, authentication and grants. REST or native branches, input/output schemas, API keys and external-provider OAuth; upstream credentials stay separate Documentation | Yes CLI MCP server over stdio manages Event Gateway resources, with optional write tools. This is gateway administration; the reviewed docs do not establish custom API-to-tool hosting Documentation | Not documented The reviewed product docs and documentation index describe webhook ingestion and delivery; they do not establish MCP tool hosting for your own APIs Documentation |
Inbound signature verification | Yes 16 authentication formats: HMAC, ECDSA P-256, HTTP Basic, exact tokens, and JWT HS256/RS256/ES256. Unknown schemes are rejected; unauthenticated flows use an explicit no_auth node Documentation | Yes Vendor source types and generic webhooks with verification Documentation | Yes HMAC, Basic auth, API keys, and provider-specific incoming source verification Documentation |
Body formats | Yes JSON, ordered XML element tree, multipart/form-data, raw Documentation | Partial Preserves arbitrary request bodies; JavaScript transformations can convert formats such as XML to JSON Documentation | Partial JSON event payloads and JavaScript transformations; no equivalent ordered XML or multipart-file parser is documented Documentation |
Native delivery destinations Counts are catalog destination types, not provider brands. Hookway counts Redis modes separately; Event Gateway includes CLI and Mock API. Configure Temporal workflow type, input, IDs and timeouts in YAML or the builder. | 15 types 15 catalog types: RabbitMQ, SQS, SNS, S3, Lambda, Redis (stream/list/pubsub/kv), Postgres, MongoDB, Kafka, webhook, MCP events, and Temporal workflow starts with configurable input, IDs and timeouts Documentation | 3 types HTTP, CLI for local testing, and Mock API. Hookdeck Outpost is a separate outbound product with 11 destination types Documentation | 1 type HTTP/HTTPS webhook endpoints; Kafka/SQS/Pub/Sub/RabbitMQ are ingest sources for outgoing projects Documentation |
Multipart / decoded file → object storage | Yes publish.payload: object writes decoded multipart file bytes to S3 or redis_kv Documentation | Not documented HTTP delivery can call your own upload handler; the reviewed docs do not establish native decoded-file publication to object storage. Outpost is a separate product Documentation | Not documented HTTP endpoints can implement uploads themselves. The documented S3 retention archive stores webhook history; it does not establish decoded multipart-file publication Documentation |
Fan-out to multiple destinations | Yes Multiple publish nodes; stop_on_failure or skip_failed Documentation | Yes One source to many connections/destinations Documentation | Yes Fan-out by event type or endpoint matching Documentation |
Traffic controls Inbound admission and downstream delivery pacing protect different parts of a system. | Yes Inbound token buckets, approximate rolling quotas, and duplicate reservations; memory, Redis, or PostgreSQL. Verified caller/tenant identities are supported Documentation | Yes Queued delivery pacing per destination and configurable deduplication rules Documentation | Yes Redis-backed ingest/API rate limits and per-endpoint delivery rate limits Documentation |
Payload transform | Yes Field mapping, JSON changes and schema validation, explicit conversions, ordered XML edits, sandboxed JavaScript, and bounded batches Documentation | Yes JavaScript transformations on connections Documentation | Yes JavaScript functions on incoming subscriptions and outgoing broker sources Documentation |
Inspect and retry failed deliveries | Yes Optional hookway-replay: inspect, download, retry individually or in batches, dismiss, and investigate via scoped operations console or API. Best-effort recovery of eligible misses after the sender’s 2xx; resumes at the failed node. No automatic re-drive. Sample → Inspect adds view-only webhook observations and downloads when file contents are retained Documentation | Yes Stored requests/events with dashboard and API retry, including bulk replay of requests. Automatic retries and manual recovery are both available Documentation | Yes Event/delivery logs and dashboard/API resend. Automatic retries use configurable linear or exponential backoff Documentation |
Payload limits Ingress size, retained artifact size, and searchable size are separate limits; these numbers are not durability guarantees. | Yes Ingress is bounded by each read_body.max_bytes. Replay max_record_bytes defaults to 16 MiB per artifact; larger artifacts become metadata-only and cannot be retried Documentation | Partial Default Developer-plan inbound limit: 10 MiB; oversize requests get 413. Body search limit: 2.5 MB, separate from storage and delivery. Larger ingest limits need arrangement Documentation | Not documented The linked guidance does not state an enforced payload-size ceiling. Check the configuration and deployment you plan to use Documentation |
Operator observability | Yes Prometheus metrics and in-repo Grafana dashboard Documentation | Yes Managed observability in the Event Gateway product Documentation | Yes Prometheus metrics (enable explicitly and check license entitlement); product delivery dashboards Documentation |
About Hookdeck Outpost
Hookdeck Outpost is a separate outbound delivery service with 11 destination types, including SQS, S3, EventBridge, Kinesis, RabbitMQ, Kafka, and webhooks. It sends your application’s events to customer destinations. Hookway receives third-party webhooks into your infrastructure. Outpost also documents webhook delivery for MCP Events, with subscription handling in your MCP server. This table compares Hookway with Event Gateway; it does not attribute Outpost’s features to Event Gateway. Hookdeck Outpost overview.
MCP also appears in event delivery: Event Gateway forwards MCP Events, while Outpost delivers event webhooks from your MCP server. Those workflows are separate from publishing your REST operations as callable tools. Hookway exposes selected APIs as tools and supports MCP Events subscriptions for compatible clients. Callback acceptance confirms receipt, not completion of an agent task. Hookway capabilities checked October 31, 2026; vendor MCP sources were checked October 31, 2026.
Sources checked for this page
Run Hookway locally
Clone the repo and start the example stack. No hosted account required.
$ git clone --branch main https://github.com/jaysongiroux/hook_way.git && cd hook_way && make dev-up