Webhook infrastructure
without the $490 cliff.

Send and receive webhooks from one dashboard — signed dispatch, exponential-backoff retries, transformations, replay, and a white-label customer portal API. $29 / $99 / $399. No enterprise jump.

Hookwell product illustration
HWHookwell — Delivery consoleSample
Sample event · billing.subscription.created

Signed, fanned out, retried — and logged.

One event, sent once from the dashboard or POST /v1/events, is HMAC-signed per endpoint, delivered to every matching endpoint, and kept in a full attempt log.

EndpointResultAttempt
app.sample/billing
Signature verified
200 · DeliveredAttempt 1
crm.sample/hooks
Signature verified · transformed
Retry scheduledAttempt 2 · backoff
data.sample/ingest
Signature verified
200 · DeliveredAttempt 1
Inbound · Stripe source
Signature verified, then normalised
Fanned outReceived
Endpoints
app.sample/billing
billing.* · signing secret per endpoint · receive inbound
Active
crm.sample/hooks
Transformed per endpoint — rename, filter, enrich
Active
Sample delivery console — illustrative endpoints and delivery attempts.At-least-once · Every attempt logged

Svix charges $20. Then $490. Nothing in between.

When your side project becomes a business, your webhook bill shouldn't 24× overnight. A SaaS team doing 200K events/mo is past the free tier and nowhere near enterprise budget — that gap is the entire business.

Most gateways pick a direction: Svix is outbound-first, Hookdeck is inbound-first (and its $39/mo Team plan caps throughput at 5 events/sec). Your app does both — so Hookwell does both, in one product and one bill.

Svix: $20/mo → $490/mo. No middle tier.
Hookwell: $29 → $99 → $399. The white-label customer portal API Svix gates at $490 is included at $99.

How it works

  1. Register endpoints
    POST /v1/endpoints with the URL, an optional signing secret, and event-type filters.
  2. Send events
    POST /v1/events — each event is fanned out, HMAC-signed, delivered, and logged.
  3. Receive webhooks
    Register Stripe/GitHub/generic sources; inbound events are signature-verified, normalized, and fanned out.
  4. Replay anything
    Every delivery keeps an immutable attempt log. Replay from the dashboard or the customer portal for 30 days.

Why Hookwell

Unified gateway

Outbound dispatch and inbound receiving in one dashboard — the thing teams currently glue together with two vendors.

At-least-once, honestly

We never claim exactly-once (impossible over HTTP to third-party endpoints). Every delivery carries a webhook-id so receivers dedupe.

Backoff + jitter + DLQ

Exponential backoff with full jitter; after final failure, deliveries park in the dead-letter queue — inspectable, replayable, never silently lost.

White-label portal API at $99

Give your customers delivery visibility under your brand — token-scoped API included in Growth, not gated at enterprise. The embeddable UI is on the roadmap.

Questions, answered honestly

Is delivery guaranteed?
No — and anyone who promises that over HTTP is selling you something. Hookwell is at-least-once: an acknowledged event is never lost, may be delivered more than once, and every delivery carries a dedupe key.
How fast are retries?
v1 runs the retry worker on a schedule (30–60s sweeps). Sub-second retry latency is a Scale-tier roadmap item, not a launch claim.
Can I transform payloads per endpoint?
Yes — rename, filter, enrich, nest, and pick fields per endpoint. Unknown transform steps are rejected at config time.
What does the inbound gateway verify?
Stripe signatures (Stripe-Signature), GitHub (X-Hub-Signature-256), or a shared secret for generic sources — per source, before anything is fanned out.

See pricing

Hookwell product visual