Apyrn Relay early access
Automatic event messages, often called webhooks, carry payments, orders, and account updates between systems. Apyrn Relay keeps those messages and their delivery history together, retries failures, and supports controlled recovery.
Example: a payment confirmation arrives while an order system is unavailable. Relay keeps the original event, retries delivery, and gives support and engineering the same recovery record.
Guided explanation
The customer problem
Payments, orders, account changes, and partner updates often arrive as automatic event messages. When one fails, support and engineering need the original event, delivery attempts, and recovery action in one place.
The better operating model
Relay receives supported event messages, checks where they came from, retries temporary failures, and lets authorized teams replay a stored event when the receiving system is ready.
The solution approach
Point supported webhook senders to Relay, forward events through controlled routes, track delivery, retry failures, and preserve recovery evidence.
Conceptual architecture
Captures incoming webhook events and stores delivery history for review and export.
Supports signature verification presets for Stripe, GitHub, and Shopify.
Supports retry scheduling, failed-event review, controlled replay, encrypted credentials, signed deliveries, and audit history.
Enterprise examples
A payment confirmation arrives while the order system is unavailable and needs automatic retry.
A Shopify order update is rejected by a fulfillment service and needs replay after the destination is fixed.
An engineering manager reviews who replayed an event and whether the recovery succeeded.
What this enables
Give support and engineering teams one shared event record.
Recover from temporary delivery failures without losing the original event.
Keep source checks, delivery attempts, replay activity, and audit history together.
Scope and qualification
Early access or design-partner pilot; public hosted availability and public SLA are not yet proven.
Relay does not replace Stripe, GitHub, Shopify, or the application receiving the event.
Recognize the problem
A webhook is an automatic message sent when an event happens, such as a payment, order, or account change. Relay keeps the event and the delivery story together.
A payment, order, or account update arrives, but the application that needs it is down or temporarily rejecting requests.
Support sees the customer problem while engineering searches logs to find the original event and failed attempts.
Managers need to know who replayed an event, when it happened, and whether delivery succeeded.
How it helps
Relay captures the incoming event and can verify supported provider signatures for Stripe, GitHub, and Shopify.
Relay forwards the event through controlled routes and retries temporary failures according to the configured policy.
An authorized person can replay a stored event after the receiving system is fixed, with audit history preserved.
Illustrative use cases
A customer-support lead sees an order that still appears unpaid. Relay shows the original payment event and failed attempts, retries delivery, and gives support and engineering the same status.
Page visual: payment confirmed, order system unavailable, retry, delivered.An operations manager sees fulfillment delays because a Shopify event was rejected downstream. Relay verifies the supported Shopify signature, preserves the event, and allows replay after the destination is fixed.
Page visual: event card, verified-source badge, and controlled replay confirmation.An engineering manager reviews an incident and needs to know who replayed an event and whether delivery succeeded. Relay keeps attempts, replay activity, receipts, and audit history together.
Page visual: a human-readable history rather than raw log lines.What teams can do
Create webhook endpoints, capture immutable events, search event details, export records, and purge payloads under policy.
Verify Stripe, GitHub, and Shopify signatures and preserve source-check evidence.
Schedule delivery attempts, review failed events, and replay an event when the destination is ready.
Use encrypted credentials, destination controls, outbound signing, signing-secret rotation, event receipts, and audit exports.
What Relay does not replace
Relay sits between supported event senders and receiving systems to improve delivery visibility and recovery. It is early access or design-partner pilot software, not a public general-availability SLA claim.
For technical teams
Relay supports endpoint creation, event capture, delivery routes, encrypted destination credentials, retry policy values, delivery history, and replay scoped to the original endpoint.
Relay has implemented signature verification presets for Stripe, GitHub, and Shopify. Other provider presets should not be claimed until implemented.
Relay includes SSRF controls, encrypted payload storage for new events, outbound HMAC signing, tamper-evident receipt hash chains, CSV audit export, usage counters, retention, metrics, and Kubernetes scrape configuration.
FAQ
A webhook is an automatic message sent when an event happens, such as a payment, order, or account change.
Relay records the event and delivery attempts, retries according to policy, and can support replay after the destination is ready.
Replay should be presented as an authorized recovery action. The product page should not imply that anyone can replay events.
The supported presets verified for the page are Stripe, GitHub, and Shopify.
Join early access to review a payment, order, account, or partner event recovery workflow with Apyrn.