Eventeer vs Hookdeck
Hookdeck focuses on receiving, routing and delivering webhooks, with a CLI for local development. Eventeer also takes in device WebSockets and WebSocket feeds, and streams events to clients. Here is how they differ.
Last reviewed: November 2026. Based on Hookdeck's public site and documentation, linked under Sources.
At a glance
| Capability | Eventeer | Hookdeck |
|---|---|---|
| Inbound webhooks | Yes: Listener URLs with token or HMAC auth, Idempotency-Key dedupe, payloads up to 256 KB. | Yes: Core product (Event Gateway): sources capture requests, connections route them to destinations. |
| Transformations and filtering | Not offered or not documented: Not offered. | Yes: JavaScript transformations, filters and deduplication per connection. |
| Outbound webhooks | Partial: Destinations you configure in your org, HMAC-SHA256 signed, at-least-once, 8 retries over about 24 hours, delivery log. | Yes: Event Gateway delivers to destinations with retries; Outpost is a separate product for sending to your customers. |
| Local development | Not offered or not documented: No CLI. | Yes: The Hookdeck CLI forwards events to localhost. |
| Device WebSockets | Yes: Ack per event, online status, last seen, downlink messages via API. | Not offered or not documented: Not described in Hookdeck's site or docs. |
| Outbound WebSocket sources | Yes: Eventeer dials a wss:// URL and reconnects with backoff. | Not offered or not documented: Not described in Hookdeck's site or docs. |
| Browser and client streams | Yes: Clients subscribe over WebSocket; reconnect with since to replay. | Not offered or not documented: Not described in Hookdeck's site or docs. |
| Event storage and replay | Yes: Kept 7, 30 or 90 days by plan; browse, filter, replay to a destination. | Yes: Requests are captured and inspectable; bookmarks and replay are documented. |
| Metrics and dashboards | Yes: Metrics on a JSON field in 1-minute buckets, plus dashboards. | Yes: Metrics on requests, events and attempts. |
| Alerts | Yes: Threshold or quiet-for-N-minutes, by email or webhook, auto-resolve. | Partial: Issues and notifications with configurable triggers. |
| Self-hosting | Not offered or not documented: Hosted service. | Partial: Outpost is open source and self-hostable; the Event Gateway is described as managed. |
| Pricing model | Monthly plans with included volume, usage-based overage and a spend cap. | See Hookdeck's own pricing page. |
When to choose Eventeer
- Your events do not all arrive as webhooks. Devices connect by WebSocket and some feeds need Eventeer to connect out to them.
- You want clients, such as dashboards or services, to subscribe to a live stream and catch up with
sinceafter a reconnect. - You want JSON-field metrics, dashboards and quiet-listener alerts in the same product that stores your events.
When to choose Hookdeck
- You want to reshape events with your own JavaScript before delivery, or filter and deduplicate them.
- You develop locally and want a CLI that forwards webhooks to localhost.
- You want isolated delivery per tenant with separate queues (delivery groups), or an open source outbound webhook service (Outpost).
Migrating
- List your Hookdeck sources and what each connection does. Note any transformations, because Eventeer has no equivalent; move that logic into your own service.
- Create one Eventeer listener per source and choose an auth mode.
- Add a destination for each service that received events, and compare its delivery log with your existing results.
- Switch the provider's webhook URL to the Eventeer listener. Send a few test events and confirm them in the event list.
- Verify the
X-Eventeer-Signatureheader in your service, then remove the Hookdeck connection.
Other options
Comparing more than these two? Alternatives to Hookdeck covers the other options and which job each one fits.
Sources
Every statement about Hookdeck on this page comes from these pages, last reviewed November 2026. Check them for current details.
Try Eventeer alongside your webhooks
Create your organization and a listener now. Choose a plan when you are ready to send traffic.