// the platform

Built for the parts you can't afford to lose.

Eight capabilities. Three responsibilities.

01 / Reliability

Event capture and durable storage

Every inbound event is persisted before we acknowledge.

A crash on either side never drops an event. The provider sees a 2xx and stops retrying because we've already written the event to durable storage, signed the receipt, and stamped it with a trace context.

Step 1Durable writeevt_01H8K9P2T7fingerprint sha256:8af9…trace 4bf92f3577b34da6…✓ persisted
Step 2202 Acceptedlatency: 47ms p99provider stops retrying
02 / Reliability

Replay and recovery

Re-deliver any event, any range, any time.

Pick the events. Pick the destinations. Replay. Pause, resume, cancel — original event identity preserved, idempotency intact. Stop writing one-off scripts at 2 a.m.

14:0015:30
outage 14:35 → 14:55
↻ replay job · job_01H8KAR4
2,184 / 2,800
03 / Reliability

Retry control

Retries on your terms, not the provider's.

Five attempts by default, exponential backoff with jitter. Per-destination policies override the defaults. Inspect, pause, or drain the queue at any time.

1st5s
2nd30s
3rd5m
4th30m
5th2h
04 / Reliability

Routing and destinations

One ingest, many destinations.

Route to internal services, third-party APIs, or staging. Per-destination headers, secrets, retry policies. Loopback prevention catches mistakes other tools just deliver.

stripe
orders-svc
billing-svc
notifs-svc
05 / Intelligence

Schema detection and versioning

Know the moment a payload shape changes.

Every payload is fingerprinted and versioned per source and event type. New fields, removed fields, type changes — surfaced before they break consumers. Annotate the fields you care about and they become indexed for search.

v3 — current
customer.id
customer.email
amount: int
currency
legacy.gateway_ref
metadata.tenant_id?
v4 — incoming
customer.id
customer.email
+ customer.tax_id_type
~ amount: decimal
currency
legacy.gateway_ref
~ metadata.tenant_id (req)
06 / Intelligence

Signature verification

Verify what comes in. Sign what goes out.

Built-in profiles for the providers you already use — Stripe, GitHub, Shopify, Adyen, Plaid, Svix — plus custom HMAC for the ones you don't. Every rejection logged with reason.

stripestripe-signature t=1714, v1=ab9f…verified
githubx-hub-signature-256 sha256=…verified
shopifyx-shopify-hmac-sha256 base64skew 312s
customx-relynq-sig key=k_2 sha256=…verified · retiring key
07 / Observability

Delivery observability

Trace every event end-to-end.

Filter by source, status, schema version, or any indexed payload field. Inspect headers, body, signature outcome, and every delivery attempt — request and response — for the full lifecycle of any event.

evt_01H8K9P26B · stripe.invoice.paid0ms — 480ms
ingest
42ms
verify
19ms
attempt 1
503
attempt 2
503
attempt 3
200
08 / Observability

Operator observability

Built on OpenTelemetry.

Traces, structured logs, and audit records into the same pipeline you already run. The platform watching your events can be watched by yours.

POST /ingest/src_01H8K962ms
service.name=relynq-api · http.status_code=202
├─ingest.persist38ms
db.system=postgresql · relynq.event.id=evt_01H8K9P2T7
├─signature.verify7ms
relynq.signature.outcome=verified · profile=stripe
└─routing.evaluate4ms
relynq.destinations=3 · relynq.workspace=ws_xyz

Try the layer underneath your events.

Free for the first 10,000 events. No card required.

Start ingesting events →See use cases