RelayHQ
RelayHQ receives provider webhooks, queues them, and delivers them to configured services with retries, routing rules, and request logs.
What RelayHQ is
RelayHQ receives provider webhooks, queues them, and delivers them to configured services with retries, routing rules, and request logs. Permanent inbound URLs can send requests to multiple destinations at once. Rules can filter requests by JSON payload path or HTTP header, with conditions combined using AND or OR logic. Failed deliveries can be retried up to five times with exponential backoff, and requests can be replayed manually from the dashboard. The site names Stripe, GitHub, and Shopify as webhook sources. RelayHQ also documents a REST API using bearer API keys or a valid session cookie, and the Free plan includes a CLI local tunnel for development. The maker says setup takes under five minutes without managing infrastructure or message brokers. The service runs on cloud infrastructure in US East (IAD). Its privacy policy says traffic uses TLS 1.2 or higher and stored API keys and passwords are hashed. The Free plan allows three endpoints and 500 requests monthly, but has no automatic retries or routing rules.
Good
- Can fan requests out to multiple destinations
- Failed deliveries can retry up to five times
- Requests can be replayed from the dashboard
- Free plan includes a local development tunnel
Watch out
- Free plan has no automatic retries
- Free plan has no routing rules
- Free plan allows 500 requests monthly
Who it suits
RelayHQ suits developers and teams that need to route provider webhooks to configured services. The Free plan includes a local tunnel, while paid tiers offer greater request capacity, retention, and routing options.
Verdict
RelayHQ centralizes webhook delivery, routing, logs, retries, and replay in a cloud service. Check the Free tier’s request cap and missing automation against your needs.
Plans and prices
From RelayHQ's own pricing page, checked 15 Oct 2026.
| Plan | Price | What it gives you |
|---|---|---|
| Free | Free | 3 endpoints · 500 requests/month · 1 destination per endpoint · 24-hour log history · 256 KB body · 60 req/min · no auto-retry · no routing rules · $0/mo |
| Starter | $29 a month | 10 endpoints · 50,000 requests/month · 3 destinations/endpoint · 30-day logs · 5 retries · conditional routing · Slack/email alerts · 1 MB body · 600 req/min · $29/mo; or $23/mo billed annually |
| Pro | $79 a month | Unlimited endpoints · 500,000 requests/month · unlimited destinations · 90-day logs · 5 seats · unlimited routing · 5 MB body · priority email support · 99.9% SLA · $79/mo; or $63/mo billed annually |
| Team | $199 a month | Unlimited requests · unlimited seats · 1-year logs · SAML 2.0/Okta SSO · audit log · 10 MB body · custom rate limits · dedicated Slack support · 99.95% SLA · custom retention · invoice billing · $199/mo; or $159/mo billed annually |
The facts
Each one read from RelayHQ's own pages, with the date it was checked.
What it does
- API
- RelayHQ documents a REST API at api.relayhq.org that uses bearer API keys or a valid session cookie.checked 5 Oct 2026
- API authentication
- Programmatic API calls use workspace-scoped bearer API keys, while the dashboard uses session cookies.checked 15 Oct 2026
- API scope
- The documented API covers workspaces, endpoints, destinations, routing rules, requests, delivery attempts, and API keys.checked 15 Oct 2026
- Automatic retries
- Paid delivery retries can run up to five times with exponential backoff.checked 15 Oct 2026
- Availability target
- The terms target 99.9% monthly uptime for the ingest layer, with higher SLA percentages on paid plans.checked 15 Oct 2026
- CLI operating systems
- The documentation says the CLI works on macOS, Linux, and Windows.checked 15 Oct 2026
- CLI package
- The official local-development CLI can be run with npx relayhq-cli or installed through npm.checked 15 Oct 2026
- CLI system requirement
- The CLI requires Node.js 18 or newer.checked 15 Oct 2026
- Credential storage
- API keys are hashed before storage and passwords are hashed with bcrypt.checked 15 Oct 2026
- Custom headers
- Destinations can receive configured authorization headers, API keys, or signatures.checked 15 Oct 2026
- Data retention
- The privacy policy lists webhook log retention as 7 days on Free, 30 days on Starter, 90 days on Pro, and one year on Team.checked 5 Oct 2026
- Delivery dashboard
- The dashboard shows HTTP status, response time, retry count, and delivery attempts in real time.checked 15 Oct 2026
- Documentation depth
- The documentation includes quick start, authentication, core concepts, API reference, CLI installation, CLI reference, and dashboard guides.checked 15 Oct 2026
- Hosting region
- The About page lists US East (IAD) as the service region and names Fly.io, Vercel, Neon Postgres, and Upstash Redis in its stack.checked 15 Oct 2026
- Independent API example
- RelayHQ.dev shows webhook ingestion through a project endpoint formatted as POST /api/in/{project_id}.checked 15 Oct 2026
- Independent auditability claim
- RelayHQ.dev describes a complete audit trail of events, delivery attempts, and system activities.checked 15 Oct 2026
- Independent feature description
- A separate RelayHQ.dev page describes sub-second ingestion, preservation of all headers, and acceptance of any content type.checked 15 Oct 2026
- Independent retry detail
- RelayHQ.dev describes configurable per-project retry policies with exponential backoff.checked 15 Oct 2026
- Independent scalability claim
- RelayHQ.dev says its API and worker services can scale horizontally to handle millions of webhooks per day.checked 15 Oct 2026
- Independent security detail
- RelayHQ.dev claims HMAC signature generation, idempotency support, and encrypted payload storage.checked 15 Oct 2026
- Ingest latency
- RelayHQ advertises webhook acknowledgement below 50 milliseconds.checked 15 Oct 2026
- Integrations
- The site names Stripe, GitHub, and Shopify as webhook sources and describes forwarding events to services configured as destinations.checked 5 Oct 2026
- Intended users
- The maker describes Starter as for indie developers and small production projects, Pro for teams running multiple production apps, and Team for engineering teams needing SSO, audit logs, and SLAs.checked 5 Oct 2026
The company
- Founded
- The company timeline says RelayHQ was founded in 2025 and publicly launched in 2026.checked 15 Oct 2026
The full review of RelayHQ
RelayHQ is a managed cloud relay for receiving, queuing, and forwarding webhooks. It is best for developers and production teams that want delivery controls without operating brokers or webhook infrastructure. The service is a strong fit once retries, routing, and retained event history matter, but its Free plan is mainly a small-volume entry point.
Overview
RelayHQ assigns permanent inbound webhook URLs, queues incoming requests, and can fan each request out to several configured destinations at the same time. The maker says a basic setup can be running in under five minutes, with no infrastructure or message-broker administration. That favors teams seeking a managed deployment; the service runs in the cloud, with US East (IAD) listed as its region, so it is less suitable when self-hosting or a different hosting location is required.
Stripe, GitHub, and Shopify are named as webhook sources, while destinations are services you configure. A REST API is documented at api.relayhq.org and accepts bearer API keys or a valid session cookie. RelayHQ says traffic is protected with TLS 1.2 or later, stored API keys are hashed, and passwords use bcrypt. It also says personal information is not sold and webhook payloads are used only to deliver events to configured destinations.
Key features
Delivery and recovery
Permanent URLs and simultaneous fan-out remove the need to build those delivery mechanics into every receiving application. On paid plans, failed deliveries can be retried up to five times with exponential backoff, and individual requests can be replayed manually from the dashboard. Those controls provide a sensible way to recover from temporary endpoint failures, although the Free plan has no automatic retry and therefore cannot demonstrate that recovery workflow.
Routing and inspection
Rules can match a JSON payload path or an HTTP header, with several rules combined through AND or OR logic. This supports selective forwarding rather than sending every event everywhere, and event inspection plus request logs help diagnose what was delivered. The Free tier has no routing rules and only 24-hour history, limiting it for troubleshooting; paid retention ranges from 30 days on Starter to one year on Team.
Development and access
The Free plan includes a CLI local tunnel for development, useful when a local application must receive provider callbacks. The API gives teams a programmatic management path, while the dashboard supplies manual replay. These are practical developer tools, but the service remains cloud-hosted rather than a self-managed deployment.
Pricing
| Plan | Price and limits | Best fit |
|---|---|---|
| Free | free; 3 endpoints, 500 requests/month, one destination per endpoint, 24-hour logs, 256 KB bodies, 60 requests/minute. No automatic retries or routing rules. | Development and very small integrations. |
| Starter | $29 a month, or $23/mo billed annually; 10 endpoints, 50,000 requests/month, three destinations per endpoint, 30-day logs, five retries, five routing rules per endpoint, 1 MB bodies, 600 requests/minute. | Indie developers and small production projects. |
| Pro | $79 a month, or $63/mo billed annually; unlimited endpoints and destinations, 500,000 requests/month, 90-day logs, five seats, unlimited routing rules, 5 MB bodies, priority email support, and a 99.9% uptime SLA. | Teams running multiple production apps. |
| Team | $199 a month, or $159/mo billed annually; unlimited requests, seats, and routing rules, one-year logs, SSO through SAML 2.0/Okta, audit log, 10 MB bodies, custom rate limits, dedicated Slack support, 99.95% uptime SLA, and custom retention. | Engineering organizations needing identity, governance, and service commitments. |
Starter is the first paid tier with retries and routing, while Pro raises capacity and adds seats, support priority, and an SLA. Team is priced for organizational controls rather than merely more throughput. The Free limits are restrictive for production: 500 requests per month, one destination per endpoint, and no automated recovery.
Platforms
RelayHQ is offered as a cloud service with API, Linux, macOS, web, and Windows access. Its CLI tunnel is specifically included on Free for local development.
Who it's for
Choose RelayHQ if you want managed webhook queuing, delivery fan-out, replay, and rule-based forwarding without running infrastructure. Starter suits a small live project; Pro fits several production applications; Team is the appropriate tier when SSO, auditability, dedicated support, and an uptime SLA are requirements. It is a weaker choice for self-hosting, strict regional hosting needs, or workloads that exceed Free limits before a paid plan is justified.
Pros and cons
- Pros: permanent URLs and multi-destination fan-out simplify integration architecture; exponential-backoff retries and dashboard replay provide concrete recovery options; JSON-path and header rules support precise routing; Free includes a local development tunnel; security practices include TLS 1.2+, hashed API keys, and bcrypt passwords.
- Cons: Free is capped at 500 requests per month and one destination per endpoint; it omits retries and routing; Starter has only five routing rules per endpoint and 1 MB bodies; cloud hosting and the listed US East region do not serve self-hosted or alternate-region requirements.
Alternatives
For a broader category comparison, see Webhook Management Software. Choose Hookdeck instead if its Developer tier's 10,000 events and three-day retention or self-hosted platform coverage better match your needs. Kiosk is a free, open-source PDF reader rather than a webhook relay. Dispatch may suit teams wanting a free 10,000-events-per-month tier with two members, while over-limit events are dropped at ingress. Hookbridge offers lower-cost message tiers beginning at 1,000 messages free and $10 per month for 5,000. Webhook Relay is worth considering for its free 150-webhooks-per-month starter allowance and self-hosted availability. Webhooker provides a free 10,000-events-per-month tier, three sources, nine destinations, and 14-day retention. WebhookX offers a self-hosted Community edition. Hookdeck Outpost is an Apache-2.0, Go-based option distributed as a binary and Docker container.
Verdict
RelayHQ is a good choice for developers and teams that want cloud-managed webhook delivery with retries, replay, routing, and progressively stronger operational controls. Starter is the practical minimum for a small production system, while Pro and Team justify their prices when capacity, seats, governance, support, or SLAs matter. Look elsewhere if you need self-hosting, another region, or a generous no-cost tier with automated retries and routing included.
Alternatives to RelayHQ
- 1
Kiosk
Free planOpen sourceAndroidiOSWebExtension8.0Free plan - 2
WebhookX
Free planOpen sourceWebAPILinuxmacOS8.0From $39 a month - 3
Svix
Free planOpen sourceWebAPILinuxSelf-hosted7.8From $20 a month - 4

Hookdeck
Free planWebAPILinuxmacOS7.7From $39 a month - 5
Dispatch
Free planWebAPILinuxmacOS7.6From $39 a month - 6

Convoy
Free planWebAPILinuxSelf-hosted7.4From $999 a month
