Hookdeck alternatives for receiving webhooks (2026)

SolidHooks is an inbound webhook platform that ingests, verifies, stores and delivers webhooks, built to be operated by AI agents as well as people.

Pricing you can predict. The billable unit is a delivery: one event routed to one connection. If you fan one event out to three destinations, that's three deliveries. Automatic retries aren't billed because they reuse the same delivery, and a manual retry of one delivery is free too. Duplicate (idempotent) requests and requests that fail signature verification aren't billed either. Replays are billed, because they create new deliveries (plans docs). Svix also says retries are free, so this isn't unique, but it does mean a bad afternoon on your side doesn't show up on the invoice.

Plans. Hobby is free for 10,000 deliveries a month with a hard cap. Launch is $29 a month for 50,000 deliveries, and Scale is $375 a month for 1,000,000 deliveries with 30-day retention; both then cost $2.75 per 100k. Enterprise is negotiated (pricing). SolidHooks bills in GBP, USD or EUR.

Built for agents. Every webhook capability is in the REST API, described by an OpenAPI spec and an llms.txt. Agents use delegated Agent Auth: they register their own key pair and the account owner approves exactly the capabilities they asked for. Hookdeck also markets an MCP server and AI-agent use cases, so SolidHooks isn't alone here.

Verification presets. GitHub, Linear, Shopify, Paystack, Nuvion, Stripe, OpenAI, Anthropic and Resend, plus Standard Webhooks, generic HMAC, Basic auth and a static API-key header (verification docs).

Beyond HTTP. A source can receive inbound email, which becomes an email.received event that routes and retries like any webhook (email ingestion). SolidHooks Connect runs a connector inside your network and delivers through it, with no inbound ports opened (private delivery). Connectors come with Launch and above.

Audit trail. Every event is stored and queryable through GET /v1/events, with a timeline of each delivery attempt (events docs).

Getting started is one call:

curl -s "https://api.solidhooks.com/v1/sources" \  -H "authorization: Bearer $SDHK_KEY" \  -H 'content-type: application/json' \  -d '{ "name": "Stripe", "provider": "stripe", "verifierConfig": { "secret": "whsec_..." } }'# The response includes the source id and its ingestUrl (https://sdhk.events/<maskId>)

Trade-offs: SolidHooks is newer and has fewer pre-built sources than Hookdeck, and its pricing page offers managed plans only, with no self-hosted option listed.

Svix is best known for sending webhooks (Svix Dispatch), and Svix Ingest is its receiving gateway. If your team already uses Svix to send events to customers, adding Ingest keeps sending and receiving with one vendor, one dashboard and one bill.

Pricing. Svix's free plan covers up to 50k messages a month across Dispatch, Stream and Ingest. Basic starts at $20 a month and Professional at $490 a month, each with 50,000 messages included, then $0.0001 per message on demand. Only attempted or transformed messages count towards usage; messages Svix filters out and retries are both free. Note that each 64 KiB chunk of payload is billed as one message, so large payloads count more than once (Svix pricing).

Regions and compliance. Svix says it runs in multiple regions to meet data-residency requirements, and lists a range of compliance certifications on its Ingest page. If your procurement team needs those, check them directly with Svix.

Where it's thinner. According to Hookdeck's own comparison page (updated 14 October 2026), Svix Ingest has 30+ pre-configured sources on Professional and above, and no dedicated queueing, field-level filtering or deduplication. That's a competitor's view, so test the features you care about yourself. Hookdeck also describes Ingest as "a newer addition to Svix's primarily outbound-focused webhook platform".

Pick it if Svix is already part of your stack and your inbound needs are fairly simple. Look elsewhere if your bill is driven by large payloads or you need queueing and deduplication on the receiving side.

Convoy is a webhook gateway that handles both directions: on its pricing page it says it can "send outgoing webhooks to your customers and receive incoming webhooks from third parties through the same platform, with retries, transformations, and delivery monitoring built in".

Pricing. The Community edition is free to self-host, with retries, message-broker support and community support through Slack and GitHub. Premium self-hosted is $999 a month and adds features such as JavaScript webhook transformations, Google OAuth, role-based access control, OpenTelemetry export, endpoint circuit breaking, white-labelling and priority support. There's also an Enterprise tier for self-managed deployments at scale, and a Convoy Cloud option with a 14-day free trial.

Pick it if your data can't leave your own infrastructure, or you want an open-source gateway you can run and change yourself. You take on running the database, the broker and upgrades.

Look elsewhere if you want a fully managed service with no infrastructure to run, or if $999 a month for the Premium features is more than your volume justifies.

For one or two providers and low volume, a home-made receiver can be enough. The minimum that holds up in production is:

1. 1.Verify before you store. Check the provider's signature against the raw request body, with a timestamp tolerance where the scheme has one. See signature verification.
2. 2.Acknowledge fast, process later. Write the event to a durable queue or table and return a 2xx straight away; do the work in a worker.
3. 3.Make processing idempotent. Providers retry, so the same event will arrive twice. Deduplicate on the provider's event ID. See idempotency.
4. 4.Retry with backoff, and stop eventually. Decide how many attempts and over how long, and where failures go. See retries.
5. 5.Keep an audit trail and a replay button. When something goes wrong, you'll want to see exactly what arrived and send it again. See replay.

The cost isn't the first version; it's maintaining verification schemes, retry state and replay tooling for every new provider over the years. If that list looks like a quarter of someone's time, a gateway is usually cheaper.