Durable delivery. Inspectable outcomes.
Delivery failures should be explainable—and recoverable.
Register your HTTPS receiver, send a signed webhook, and follow every attempt from acceptance through retry or final outcome.
Open workspaceSign in with GitHub. Create one private workspace.
From event to outcome
- 01
Configure a receiver
Register a public HTTPS endpoint and save its one-time signing secret.
- 02
Send an event
Acceptance commits the event and delivery work durably before dispatch.
- 03
Inspect and recover
Follow immutable attempts, scheduled retries, and confirmed manual replays.
Built for honest delivery semantics
At-least-once delivery with signed payloads, bounded retries, and auditable recovery. Receivers must verify signatures and deduplicate events. An accepted event is not yet a successful delivery.
A workspace for operational clarity
Inspect HTTP results, timing, failure classifications, and the relationship between an original delivery and its replay. Use synthetic data in this public demo.