Webhook Relay
Webhook Relay, shown as Signalpost on the live site, sits between services that send webhooks and the systems that need them. It checks each message is genuine, ignores repeats, delivers it with retries, and parks failures with the reason so they can be replayed. A console shows every event and attempt, and the same design is written a second time for AWS.
Measured numbers
- Tests
- 433
- Browser tests
- 18
- Lighthouse performance
- 97
- Accessibility
- 100
- Best practices
- 100
- SEO
- 100
Home page, mobile. Copied from the showcase's own README on 24 October 2026.
Open the live site (opens in a new tab) relay.phoenixcodes.org
On a phone
At desktop width
What it proves
- Signature checks for four provider styles, including a timestamp tolerance.
- Duplicate events are recognised by idempotency key and never delivered twice.
- Retries with backoff, then a dead-letter queue and one-click replay.
- One design written for Cloudflare and again as an AWS CDK template, with the AWS version tested but never deployed.
How this adapts to your project
Register your own sources and secrets, point destinations at your services, and set the retry schedule that suits them. If your company runs on AWS, the CDK version shows the same design on Lambda and queues, ready to adapt.