Frequently Asked Questions

Create a source in the dashboard to receive a unique inbound URL. Point your provider — GitHub, Stripe, Shopify, or any service that sends HTTP webhooks — at that URL. Duerelay logs every inbound event and forwards it to your registered delivery endpoints in real time.

No code changes or middleware are required on your end. The inbound URL is stable and does not change unless you rotate it.

Yes. The Events page shows every inbound event with its HTTP headers, content type, and full JSON body. Expand any row to inspect the raw payload, copy it, or trigger a manual re-delivery to any registered endpoint.

Failed deliveries are retried automatically with exponential back-off. When all retry attempts for an event are exhausted an Incident is created and visible in the Incidents view. You can also trigger a manual replay from the Events or Endpoint Deliveries pages at any time.

Yes. Owners can invite teammates by email and assign one of three roles:

Owner — full access including billing and quota management.
Admin — can create and manage endpoints, sandboxes, and invite other members.
Member — read-only access to event logs, deliveries, and incidents.

Invitations are sent by email and expire after 7 days if not accepted. Members can be removed or have their role changed at any time from Settings.

Yes. Sandbox organisations share the same ingest pipeline and event model as production but operate under relaxed quotas with no billing requirements. You can send test webhooks, inspect payloads, and exercise the full delivery flow before going live.

Inbound events are metered against your plan quota. When the quota is exhausted the admission layer begins blocking new events and an enforcement banner is displayed in the dashboard. No events are silently dropped — blocked events return a clear HTTP error to the sender.

Upgrading your plan or waiting for the next quota period lifts the restriction automatically. Owners can view current usage and upgrade from the Billing page.

Yes. Alert channels are live on all paid plans. In-app alerts are included from Starter, email alerts from Core, and Slack / Teams notifications are available as an add-on. Alerts fire when delivery failures occur or when an incident is opened. Configure channels and thresholds from the dashboard.

Yes. Agent SDKs are available from Starter and above. They provide a typed execute endpoint for triggering webhook-driven actions programmatically, with per-agent credentials and policy enforcement built in. The CLI is available at get.duerelay.com for managing sources, endpoints, replays, and tailing event streams from the terminal.

Yes. Relay transforms let you apply field-level filtering, header injection, and body modification before delivery. Outbound dispatching supports conditional routing rules — route specific event types to specific endpoints, strip sensitive fields before forwarding, or enrich headers. Configure transforms and routing from the Relay Setup page.

Yes. Compliance export is available on Scale and Enterprise plans. Export audit trails and event history via the dashboard or the Metrics API. The immutable audit trail is included on all paid plans — 60 days on Starter and Core, 90 days on Scale, and 365 days on Enterprise.

Policy gates enforce rules before an event is executed or an agent action proceeds. Three gate types are available: budget (spend limits), rate (throughput caps), and content (payload validation). Policies are evaluated at admission time and block non-conforming requests with a clear rejection reason. Available from Starter and above.

Yes. OTEL traces are available on Scale and Enterprise plans. Every event execution — from ingress through policy evaluation, delivery, and agent action — is recorded as a trace. View traces in the dashboard Traces page or export them to your own observability stack.

Bundles execute multiple actions atomically with rollback. Group a sequence of agent actions — such as provisioning an entitlement, sending a confirmation, and updating a ledger — into a single bundle. If any step fails, preceding steps are rolled back. Bundles are available on all paid plans.

Yes. Approval gates let you require human sign-off before an agent action or bundle proceeds. When an action triggers an approval gate, execution is paused and a notification is sent to the configured approver. Once approved, execution resumes automatically. Configure approval rules from the Governance page.

Inbound ingress policies can validate webhook authenticity at admission time. Outbound re-signing — adding a Duerelay-issued signature header to forwarded requests — is not yet available. Signature headers from the original sender are forwarded unchanged, so your endpoint handler should still verify against the raw body.

Yes. The ingest proxy enforces a per-request payload size limit. Requests that exceed this limit are rejected with a 413 Payload Too Large response and are not stored or forwarded. This limit applies to the raw request body before any processing.

Not yet. All endpoints share the same system-level retry schedule and back-off parameters. Per-endpoint retry limits, timeouts, and back-off curves are planned.

Duerelay currently operates in a single region. Inbound and outbound latency depends on geographic proximity to that region. Multi-region ingestion and delivery routing is a planned expansion.

Individual event replay is available today from the Events page. Bulk replay — replaying a filtered set of events (by time window, event type, or failed status) in a single operation — is planned.

Planned. Outbound re-signing — adding a Duerelay-issued signature header to forwarded requests so your endpoint can verify the delivery came from the control plane — is on the roadmap.