RelayKit
relaykit.io
- Free plan
- Web
- API
What RelayKit is
RelayKit is a cloud service and API for receiving webhook events from third-party services, inspecting and verifying them, storing records, and forwarding them. One incoming event can go to multiple destinations in parallel, with delivery tracking and retries handled separately for each destination. Failed deliveries can be retried automatically up to 20 times, and events can be replayed manually.
Inbound signature verification supports Stripe, GitHub, Shopify, Twilio, SendGrid, Paddle, Clerk, and Resend. Security controls include IPv4 and IPv6 allowlisting, configurable rate limits, and audit records for rejected requests. RelayKit says it forwards the original request body and headers, except for specified hop-by-hop headers. Its CLI can forward webhooks to a local development server and requires Node.js 18 or later. Hobby is free and allows 1,000 webhooks per month; Pro costs $9 a month and Team costs $29 a month. Team adds Schema Sentinel for payload structure changes, Time Machine replay, and priority support. A 14-day trial is listed.
Who it suits
The maker describes Hobby as suited to side projects and local development, Pro for solo developers shipping products, and Team for teams handling serious webhook volume.
Good to know, and what to watch
- Routes each event to multiple destinations in parallel.
- Retries failed deliveries up to 20 times.
- Supports signature verification for eight named services.
- Team includes Schema Sentinel and priority support.
- Hobby allows 1,000 webhooks per month.
- Hobby retains logs for 24 hours.
- The local development CLI requires Node.js 18 or later.
Plans
Every plan and priceHobby
Pro
Team
Free plan · 14-day trial
Getting started
- Open the RelayKit website or API
- Choose Hobby, Pro, or Team
- Configure an inbound webhook endpoint
- Set signature verification, allowlisting, or rate limits
- Add forwarding destinations and fan-out routes
- Install @relaykit/cli with Node.js 18 or later for local forwarding
Limits to check
Hobby includes 1,000 webhooks per month, one project, and 24-hour log retention. Pro raises the allowance to 100,000 webhooks with five projects and 30-day retention; Team provides 500,000 webhooks, 20 projects, and 90-day retention.
The Club's review
RelayKit is a cloud webhook service for capturing, verifying, inspecting, storing and forwarding events from third-party systems. It suits developers running anything from a local side project to several production integrations, especially when one event must reach multiple destinations reliably. The main decision is whether its project, volume and retention ceilings match your workload.
Overview
RelayKit combines inbound signature checks with delivery management. It keeps incoming payloads available for inspection, forwards the original request body and headers (excluding specified hop-by-hop headers), retries failed deliveries and allows manual replay. Fan-out routing sends one webhook to several endpoints in parallel while tracking each endpoint independently, so a failure at one destination does not obscure the status of the others.
Hobby is usable for experiments and local development, but one project, 1,000 webhooks per month and 24-hour logs leave little room for a busy production integration. Pro is the sensible baseline for a solo developer operating a real product. Team is aimed at higher-volume deployments that need longer history, schema-change detection and responsive support.
Key features
Delivery, retries and replay
Automatic retries can run for up to 20 attempts, and manual replay provides a way to resend events after an endpoint is repaired. Fan-out routing, offered on Pro and Team, delivers in parallel and retries each destination separately. That separation is valuable when only one downstream system is unavailable. Hobby includes manual replay but not the Pro retry allowance or fan-out controls.
Verification and security
Inbound verification supports Stripe, GitHub, Shopify, Twilio, SendGrid, Paddle, Clerk and Resend, reducing the need to implement provider-specific checks yourself. IPv4 and IPv6 allowlisting, configurable rate limits and audit records for rejected requests add useful perimeter controls for production endpoints.
Inspection and development
Event inspection and stored logs make it possible to examine deliveries before diagnosing an application. The published @relaykit/cli can forward webhooks to a local server; its documentation requires Node.js 18 or later. Team's Schema Sentinel watches for changes in webhook payload structure, a worthwhile safeguard when provider changes could silently break consumers. Team also adds Time Machine replay.
Pricing
Hobby — free
Hobby includes 1,000 webhooks per month, one project, 24-hour log retention, signature verification, manual replay and the local development tunnel CLI. It fits side projects and development environments. The single-project cap and short history make it a poor choice for multiple production integrations or investigations that span more than a day.
Pro — $9 a month
Billed recurring monthly, Pro raises the allowance to 100,000 webhooks, supports five projects and retains logs for 30 days. It adds up to 20 retries, IP allowlisting, rate limiting, email and Slack incident alerts, and fan-out routing. A 14-day free trial lets a solo developer assess the workflow before paying. This is the strongest balance for a live product, although teams needing more projects, longer retention or schema monitoring will outgrow it.
Team — $29 a month
Also billed recurring monthly, Team allows 500,000 webhooks per month across 20 projects and keeps logs for 90 days. It includes Pro features plus Schema Sentinel, Time Machine replay and priority support, with a 14-day free trial. The extra capacity and operational features suit teams handling serious webhook volume; smaller workloads may not justify the higher monthly cost.
Platforms
RelayKit is delivered as a cloud service through its API and web interface. Local forwarding is available through the CLI, which requires Node.js 18 or later.
Who it's for
Choose RelayKit Hobby for a side project or local development setup that can stay within 1,000 monthly webhooks and one project. Pro is designed for solo developers shipping products who need dependable retries, routing, alerts and a month of logs. Team is the fit for teams with substantial volume, many projects or a need to detect schema changes and obtain priority support. It is less suitable when self-hosting is a requirement, since RelayKit is cloud-deployed.
Pros and cons
Pros
- Independent fan-out delivery: parallel destinations have separate tracking and retry behavior.
- Broad signature coverage: verification supports eight widely used providers.
- Useful recovery tools: retries up to 20 attempts, manual replay and Team's Time Machine replay address different failure scenarios.
- Production safeguards: IP allowlists, rate limits and rejected-request audit records strengthen endpoint control.
- Clear upgrade path: monthly allowances grow from 1,000 to 100,000 and 500,000, with retention and project counts rising as well.
Cons
- Very limited free tier: one project, 1,000 monthly webhooks and 24-hour retention constrain ongoing production use.
- Key routing controls start at Pro: Hobby lacks fan-out, long retry handling and incident alerts.
- Schema monitoring is restricted to Team: smaller teams cannot use Schema Sentinel without the higher plan.
- Cloud-only deployment: organizations requiring a self-hosted service will need another option.
Alternatives
Hookdeck is a better fit when cross-platform clients, desktop operating systems or self-hosting options matter, and its free Developer plan allows up to 10,000 events with three-day retention.
Convoy suits teams wanting a self-hosted option with incoming and outgoing webhooks, automatic retries and message-broker support on its free Community plan.
HookBytes is worth choosing when unlimited self-hosted webhooks and an MIT-licensed open-source plan are priorities.
Svix is an alternative for buyers who need a published 99.9% uptime SLA, 200 messages per second and 50,000 free messages per month on Basic.
Webhook Management is suited to a lower-cost API/web option whose Starter tier includes 10,000 requests monthly and seven-day logs.
webhook.co is the choice for teams prioritizing an Apache-2.0 open-source core that can be self-hosted.
HookRelay fits small workloads needing a simple web-only service, with its free plan limited to one channel and 100 requests per day.
Dispatch is an option for teams that can work within public projects and three days of history on its free tier.
Browse the Webhook Management Software list for more options.
Verdict
RelayKit is a strong choice for developers and teams that need verified, inspectable webhook delivery with independent fan-out retries and a straightforward growth path from free development use to high-volume operations. Choose it for those controls and its provider coverage; look elsewhere if self-hosting is mandatory or if your workload needs more generous free-tier retention and project limits.
The verdict
RelayKit covers webhook verification, routing, retries, and replay, with plan allowances ranging from 1,000 to 500,000 webhooks per month. The free Hobby plan has shorter log retention and fewer projects than the paid plans.
Questions people ask
Is there a free plan?
Yes. Hobby costs nothing and includes 1,000 webhooks per month, one project, 24-hour log retention, signature verification, manual replay, and the local development tunnel CLI.
What do the paid plans cost?
Pro costs $9 a month, billed recurring monthly. Team costs $29 a month, also billed recurring monthly.
Is a trial available?
Yes. Pro and Team each include a 14-day free trial.
Which services support signature verification?
RelayKit lists Stripe, GitHub, Shopify, Twilio, SendGrid, Paddle, Clerk, and Resend.
Does RelayKit retry failed deliveries?
Yes. Automatic retries can run up to 20 attempts, and events can also be replayed manually.
Who operates RelayKit?
The terms state that RelayKit is operated by IOGravity.
What the maker publishes
- Fan-out
- RelayKit can deliver each incoming webhook to multiple destinations in parallel, tracking and retrying each destination independently. source
- Integrations
- Inbound signature verification supports Stripe, GitHub, Shopify, Twilio, SendGrid, Paddle, Clerk, and Resend. source
- Local development
- The published @relaykit/cli can forward webhooks to a local development server; the documentation says it requires Node.js 18 or later. source
- Operator
- The terms state that RelayKit is operated by IOGravity. source
- Payload handling
- RelayKit says it forwards the original request body and headers without modifying them, apart from specified hop-by-hop headers. source
- Plan limits
- The listed monthly webhook allowances are 1,000 for Hobby, 100,000 for Pro, and 500,000 for Team. source
- Retries and replay
- RelayKit automatically retries failed deliveries, with up to 20 attempts, and supports manual replay. source
- Schema monitoring
- Schema Sentinel detects changes in webhook payload structure and is listed as a Team feature. source
- Security
- The service offers inbound signature verification, IPv4 and IPv6 IP allowlisting, configurable rate limits, and audit records for rejected requests. source
- Support
- The Team plan includes priority support. source
- What it does
- RelayKit captures, inspects, verifies, stores, and forwards webhook events from third-party services. source
- Who it is for
- The maker describes Hobby as suited to side projects and local development, Pro to solo developers shipping real products, and Team to teams with serious webhook volume. source
Checked against the maker's pages on 8 Oct 2026.