RelayWarden
The RelayWarden platform

Inbound and outbound events.
One durable path.

Receive payments, shipping, CRM, and SaaS webhooks, or pull from APIs that cannot push. Preserve the original request, deliver with controlled retries, and keep the evidence your team needs.

Request access →See plans →
01
The sequence

Receive, persist, deliver,
and prove it happened.

Reliability is not a retry button. It is a sequence that makes failure visible and recoverable at every step.

Delivery receiptevt_01J7…A91F
✓Received from Stripe
✓Stored safely, exactly as sent
↻First try: store answered 503
✓Delivered: 200 OK, attempt 2
02
What the sequence guarantees

Three stages,
12 guarantees.

Every event crosses the same three stages, whichever service sent it. Each stage holds a promise you can hold us to.

On arrival

Reliable intake

  • Instant acknowledgement
  • Never throttled on intake
  • Persist before delivery
  • Original payload and headers preserved
On the way out

Delivery control

  • Parallel or strict sequential delivery
  • Per-project concurrency caps
  • Configurable endpoint timeout
  • Exponential backoff & circuit breakers
After the fact

Proof and operations

  • Every attempt recorded
  • Delivery history and response evidence
  • Project-level stats and timelines
  • Alerts on failed webhooks
03
Unified indexed search

Type once. Search
every gateway.

An order ID, a customer email, a reference: one search matches the exact text across every project and gateway at once on eCommerce and above, over payloads that stay encrypted at rest, and opens the full delivery history behind any hit.

✓Exact-text match, across gateways and projects (eCommerce+)✓Indexed per tenant, encrypted at rest✓From match to full receipt in one click
13373 matches · 2 projects
All projectsStripeRedsysShipping
shipment.deliveredShipping09:12
order #1337
order.shippedShippingyesterday
order #1337
payment.succeededStripeyesterday
order #1337 · €128.40
Searches run over encrypted payloads, indexed per tenant and never stored in plaintext.
04
Where your events live, and who can read them

Connected widely.
Guarded narrowly.

Integrations

What it talks to
  • Inbound payment, shipping, CRM, and SaaS webhooks
  • Outbound and pull connectors
  • Generic HTTP pull sources
  • Dispatch proxy mode for first-party analytics

Sovereignty and security

Where it runs
  • EU data residency by default
  • No shared IPs in the ingest path
  • Destination ownership verified before delivery
  • Requests your access rules reject are never billed

Data protection

What it holds
  • Encrypted in transit and at rest
  • Per-tenant envelope encryption
  • Search never reads raw payload text
  • Controlled retention boundaries
A deliberate trust boundary

We don’t need or want
your signing secret.

Any intermediary that holds your signing secrets could alter, or even forge, the very requests it delivers. RelayWarden forwards the request untouched, and your backend verifies Stripe’s, or any provider’s, signature end-to-end, exactly as if the relay were not there.