Dispatch

Overview

Dispatch is a cloud service that verifies, processes and routes webhooks to chat platforms and HTTP endpoints. It suits developers and teams coordinating integrations across several services. Its strongest case is the combination of payload shaping and multi-destination delivery; the main constraint is that private projects require a paid plan.

Key features

Dispatch checks incoming webhooks against provider-specific signatures before storing them, rejecting requests that fail verification. That gives teams a useful safeguard at the point of entry, alongside AES-256-GCM encryption for destination URLs, bot tokens and OAuth tokens at rest and TLS 1.2 or higher for client and delivery traffic.

After verification, events can be filtered using header or body fields, transformed with JSONata expressions and fanned out to linked destinations. A single template can render Discord embeds, Slack Block Kit messages and Telegram HTML through platform-specific variants. This is useful when one source event needs different treatment across several channels, rather than a simple one-to-one forward.

Failed deliveries are retried with configurable exponential backoff, up to seven attempts by default. Event inspection and replay help with tracing and resending events, though history is limited by plan. Documented sources include GitHub, GitLab, Bitbucket, Jira, Linear, OpenAI, Shopify, Stripe, Vercel and Sentry; destinations include Discord, Slack, Telegram, Google Chat, Webex and generic webhooks.

The CLI securely tunnels webhook events to a local development server, with precompiled binaries for Linux, macOS and Windows. Project-scoped API keys use the dsp_ prefix. TOTP multi-factor authentication, organization roles and row-level security provide additional access controls. Dispatch runs on SOC 2 compliant cloud infrastructure and aims to respond to vulnerability reports within 48 hours.

Pricing

The Free plan costs nothing and includes 10,000 events/mo, 3 days of history and 2 members. It is restricted to public projects, and over-limit events are dropped at ingress, so it is best for evaluation or workloads that can tolerate that cap and short retention.

Team costs $39 a month, billed monthly. It raises the allowance to 50,000 events/mo, history to 7 days and membership to 5, and permits private projects. Overages cost $0.03/1K, with an 80% alert; priority support is included. This is the practical step up for a small team needing private routing, but its short history may not suit longer investigations.

Growth costs $399 a month, billed monthly, and provides 500,000 events/mo, 30 days of history, 25 members and private projects. The same $0.03/1K overage and 80% alert apply, while support becomes dedicated. It fits larger teams with heavier volume or a need for a longer event record; smaller workloads may not justify the jump in monthly cost.

Platforms

Dispatch is available as a cloud service across API, Linux, macOS, web and Windows. The CLI tunnel supports local development on Linux, macOS and Windows. Its cloud deployment will not suit teams seeking a self-hosted deployment.

Who it's for

Dispatch is a good fit for developers and teams that need to verify incoming events, inspect and reshape payloads, and deliver them to multiple destinations with retries. It is less suitable for private-project use on a free budget, workloads that may exceed the free ingress cap, or teams that need self-hosting.

Pros and cons

• Pros: Signature checks happen before storage, and encrypted credentials plus multi-factor authentication strengthen the security model.
• Pros: Filters, JSONata transforms and platform-aware templates let teams adapt one event for multiple destinations.
• Pros: Retries, inspection and replay offer useful delivery oversight.
• Cons: Free projects must be public, and events beyond the 10,000-per-month cap are dropped at ingress.
• Cons: Team includes only 7 days of history; longer retention and larger membership require the substantially more expensive Growth tier.
• Cons: Dispatch is cloud-only, which rules it out for teams that require self-hosting.

Alternatives

Hookdeck is worth comparing for a free option with up to 10,000 events, 3-day retention and one user; its free trial and Linux, macOS, Windows, web, API and self-hosted platforms may also suit a different setup.

Webhook Relay may fit a very small routing need: its free tier allows 150 webhooks/month, up to 2 destinations and 1 input, and it supports self-hosting.

Convoy is an alternative for teams seeking self-hosting; its free Community plan includes one user, one organisation, incoming and outgoing webhooks, automatic retries and message broker support.

Hook0 suits a narrow free workload of one developer and one application, with 10 event types, 10 subscriptions, 100 events/day and 7 days of retention; extra events are blocked.

Repost offers a free plan with a 50K events/mo hard cap, one seat, three buckets and 30-day history, making it an option when a longer free history matters more than team size.

Svix is another freemium choice; its Basic plan costs $20 a month and includes a 99.9% uptime SLA, 200 messages/second, 30-day payload retention and 50k free messages/month.

Webhook Management has a free Starter plan with 10,000 API requests/month, all services, 7-day log retention and basic analytics.

FastHook is free during launch and supports receiving webhook traffic, routing to destinations, inspecting requests and attempts, and retrying.

Verdict

Choose Dispatch if you need signature verification, flexible payload handling and reliable fan-out to chat and HTTP destinations in one cloud pipeline. Its paid tiers add private projects, more event capacity and longer history, but the public-only free tier and ingress drops make it a poor fit for private projects or workloads that cannot risk exceeding the cap. Look elsewhere if self-hosting is essential.