Products Developer tools
Available for trialWebhook delivery & diagnostics

HookRelay

Make the handoff between systems visible.

HookRelay is a service for teams that send webhooks to customer or partner systems. Give each event an inspectable delivery path, with the context needed to investigate failures and retry a handoff.

Guided evaluation · Technical discovery · Trial access through our team

REST APIPHP SDKNode SDKCLI
01

Give every outbound event a durable delivery record

02

Recover transient failures without losing order

03

Let support teams replay safely with evidence

Built around the
work that matters.

Explore how HookRelay works, then talk with us about trial access for your workflow.

01

Signed event delivery

Payload signatures can help receiving services verify an event came from the configured sender.

02

Retry policies

Retry settings can handle transient delivery failures according to a defined policy.

03

Delivery history

Inspect attempt records, response codes, and timing when an integration needs attention.

04

Alerts and replay

Failure alerts and explicit replay Controls can support operational investigation.

A clear path from
setup to everyday use.

  1. Register the destination

    Configure a receiving endpoint and its signing and Retry settings.

  2. Submit an event

    Your application can hand an event to the service for delivery.

  3. Follow the attempts

    Review delivery records, investigate errors, and replay when appropriate for the receiver.

How HookRelay
fits together.

A clear division between the product interface, processing layer, and the systems your team already owns.

01Event intake

Accept authenticated events with stable IDs, destination scope, and idempotency keys.

02Delivery workers

Sign payloads, enforce timeouts, classify responses, and apply retry schedules.

03Operations console

Inspect attempts, redact bodies, pause endpoints, and replay selected events.

Built for integration,
not a closed box.

Trial onboarding confirms the exact environment, product boundary, and success criteria for your implementation.

Platforms & surfaces

REST APIPHP SDKNode SDKCLI

Connects with

AuditKitQueueWatchSubBridgeOpsBoard alerts
SignaturesTimestamped HMAC
RetriesExponential schedule with terminal state
OrderingPer-endpoint ordering option
PayloadsJSON with configurable retention
ReplaySingle event or filtered batch

Deliberate boundaries
from the beginning.

  • SSRF-resistant destination validation
  • Encrypted endpoint secrets with rotation
  • Payload redaction and retention limits
  • Permissioned pause, edit, retry, and replay actions

Made for real workflows.

SaaS platform teams

For products notifying customers when business events occur.

API providers

For teams that need clearer support conversations about outbound integrations.

Internal integration teams

For organizations linking services through asynchronous HTTP events.

Evaluate HookRelay
against real work.

We scope the trial around one meaningful workflow, the environments you use, and evidence your team can assess.

  1. 01

    Create a sandbox endpoint and signing secret

  2. 02

    Send success, timeout, throttling, and failure scenarios

  3. 03

    Verify receiver idempotency and signature checks

  4. 04

    Review retry, retention, and alert policy

What the evaluation includes

Product access for the agreed scope, technical onboarding, implementation guidance, and a review of the findings.

Discuss trial access ↗

Explore with confidence.

A closer look at the scope and trial experience for HookRelay.

How can I try HookRelay?

HookRelay is available through a guided trial. Tell us about your requirements, platform, and evaluation goals; our team will discuss fit, access, and the right trial scope with you.

Do receivers need to handle duplicate events?

Yes. Retries and manual replay can repeat an event. Receiving applications should use event identifiers and idempotent processing where duplicate effects can cause problems.

Can an HTTP success response prove the business action completed?

No. A successful HTTP response only describes the receiver response to that attempt. The receiving application remains responsible for its own business processing and reporting.

Bring us your
real workflow.

Share your platform, requirements, and evaluation goals. We'll discuss the product and arrange a focused trial where it fits.

Request a HookRelay trial ↗