Convoy Alternative: Hosted Outbound and Inbound Webhooks Without Running a Gateway

Webhook Relay is a hosted alternative to Convoy: you get outbound webhooks to your customers and inbound webhook forwarding without deploying, upgrading or paging anyone for a gateway. Convoy is a capable self-hosted webhook gateway that sends and receives, but the paid features need a $999/month Premium licence and your team runs the infrastructure. Webhook Relay's Outbound Gateway is included from $9.99/month with Standard Webhooks signing, retries, per-endpoint rate limits and 35 days of delivery history, and the same account receives webhooks, delivers into localhost and private networks, and runs tunnels.

Update, October 2026: an earlier version of this page compared inbound delivery only and said Convoy was the option for outbound. Webhook Relay now sends webhooks to your customers, so this page covers both directions.

TL;DR

• Want to stop operating webhook infrastructure? Webhook Relay is fully hosted. No Postgres, no workers, no upgrades.
• Must self-host for data-residency or policy reasons? Convoy (or another self-hostable option) is the better fit; Webhook Relay's Outbound Gateway is hosted only.
• Worried about Convoy's momentum? Releases continue, but most recent commits come from one contributor. Read the status section below and check for yourself.
• Moving off Convoy? Receivers switch to Standard Webhooks verification, and a compatible existing secret can be imported so customers keep their key. See the Convoy migration guide.

Convoy's status in October 2026

Here's what we could verify on 2026-10-11:

• Releases continue. The frain-dev/convoy repository published v26.8.0 on 2026-09-28 and was last pushed on 2026-09-30. It isn't archived.
• Maintenance is concentrated. Of the last 100 commits since July 2026, 91 were by one contributor.
• The commercial offer is still listed. The pricing page shows a free self-hosted Community edition, a $999/month self-hosted Premium licence, custom Enterprise, and a 14-day trial (cloud trial limited to 100 events/day). Ongoing Convoy Cloud pricing isn't published there.
• The licence is source-available. Convoy is under the Elastic License 2.0, not an OSI open-source licence.
• A competitor says more. Svix's Alternatives to Convoy page (May 1, 2026) says the company behind Convoy "essentially wound down" and that measured uptime was "below 99.0% over the last 12 months". We couldn't verify either claim independently.

None of this means Convoy stops working tomorrow. It does mean a team choosing it today should plan to own the deployment, and possibly the code, for the long term.

Convoy vs Webhook Relay

Convoy details from getconvoy.io, pricing and GitHub, checked 2026-10-10/11. Webhook Relay outbound is on every plan, Free included: Basic includes 100,000 messages a month and 10,000 customers, Business 1 million and Pro 5 million messages with unlimited customers, and message packs add more (+1 million for $20 on Business).

What self-hosting actually costs

Convoy Community is free to download. Running it isn't:

• Infrastructure. The gateway processes plus a PostgreSQL database sized for your retention, with backups and failover.
• Upgrades. Following releases, testing migrations and rolling them out without dropping in-flight deliveries.
• On-call. When a customer says "we never got the event", the person debugging is on your team, and so is the person paged when the worker falls over at 3 a.m.
• The licence for the useful parts. Portal links, transformations, circuit breaking and advanced retention are Premium features at $999/month, on top of the infrastructure you run.

For a platform team whose job is infrastructure, that can be a fine trade. For a product team that needs to ship webhooks because a customer asked for them, the hosted path is usually cheaper in engineering time, not just in dollars.

Where Convoy is strong

• Self-hosting. If your policy says webhook payloads never leave your infrastructure, a self-hostable gateway is the right category.
• Both directions in one gateway, with a control-plane/data-plane design on PostgreSQL.
• Static outbound IPs through your own forward proxy, which receivers can allow-list.
• Source access. You can read and patch the code.

Where Webhook Relay is different

Hosted, with nothing to operate

You register event types, customers (consumers) and their endpoints, then publish. Webhook Relay owns the durable queue, retries, per-endpoint pacing, health tracking, signing, history and recovery. A 202 from the publish API is a durable receipt.

Standard Webhooks for your customers

Every delivery carries webhook-id, webhook-timestamp and webhook-signature, so your customers verify with any Standard Webhooks library. You can check a captured request with the free verifier.

Recovery built in

Every attempt with its response is kept for 35 days. Retry one delivery, recover everything that failed during a customer's outage, or replay what was skipped while an endpoint was paused, from the dashboard, the API or MCP.

Inbound into private networks, tunnels and a free Bin

The same account receives provider webhooks and delivers them into localhost, internal services and Kubernetes through the relay agent, runs tunnels, and includes the free Webhook Bin. Point an outbound test endpoint at a Bin to watch your own signed deliveries and retries arrive.

What we don't do yet

To be fair about the gaps: no customer portal yet, no queue destinations, no static IPs for outbound, no self-hosted Outbound Gateway, TypeScript and Go SDKs only (plus REST and MCP), and no HIPAA or PCI.

When to pick which

Choose Convoy if:

• you must self-host and are ready to run and patch the gateway yourself,
• you need static outbound IPs through your own proxy or portal links today,
• you're comfortable with the project's current maintenance level.

Choose Webhook Relay if:

• you'd rather not operate webhook infrastructure at all,
• you want Standard Webhooks signing, retries, rate limits and 35-day history on every plan, Free included,
• you also receive webhooks and need delivery into localhost or private networks.

Moving off Convoy changes the signature scheme your customers verify (X-Convoy-Signature becomes Standard Webhooks), so their receiver code changes. Their key doesn't have to: if an endpoint's current secret is 32-100 base64 characters, pass it as secret when you create the endpoint on Webhook Relay. The Outbound Gateway is generally available on every plan, Free included. Read the Convoy migration guide, see how outbound webhooks work, or compare every option in webhooks as a service compared.