Skip to content
Pricing

Free during beta. Honest about the rest.

HookWatch is in early beta. The Free tier is free while we build; paid tiers below are available now through Paddle checkout.

Free

$0 /mo

For side projects and trying HookWatch out.

Events / 30 days
10,000
  • 10,000 events / month
  • 1 project, 3 endpoints
  • 1-day payload retention
  • Manual replay

Pay as you go

$0 /mo

Pay only for what you use. Best for irregular or seasonal traffic.

Events / 30 days
0
  • $1.50 per 100,000 events
  • 7-day payload retention
  • Replay and batch replay
  • Spending limit protection

Developer

$12 /mo

Predictable monthly pricing with included events and lower overage rates.

Events / 30 days
100,000
  • 100,000 events included
  • $1 per extra 100,000
  • 7-day payload retention
  • Replay and retry policies

Startup

beta
$39 /mo

Growing teams with steady webhook volume.

Events / 30 days
1,000,000
  • 1,000,000 events included
  • $0.70 per extra 100,000
  • 30-day payload retention
  • Team access and advanced analytics

Business

$99 /mo

High volume with priority support.

Events / 30 days
5,000,000
  • 5,000,000 events included
  • $0.50 per extra 100,000
  • 90-day payload retention
  • Priority support

The Free tier needs no card. Paid tiers check out through Paddle. Event allowances are per 30 days. "Planned" features are not available yet, and this pricing may still change.

High-volume & custom infrastructure

Need millions of events, longer retention, or VPC deployment?

Custom volume tiers (10M+ events/mo), 90-day to 1-year delivery retention, dedicated instances or VPC peering, invoice billing (ACH/Wire with Net 30), and a shared Slack channel for your engineering team.

Compare tiers

The same three tiers, side by side.

 FreeProTeam
Endpoints & replay/retry
Failure analysis & incidents
Slack & webhook alerts
Delivery retentionStandardLongerAdvanced
Team membersLimitedMoreMore
Alert rulesStandardMoreMore
Audit exports——
Workspace controls——
SSO (SAML 2.0 / OIDC)
SupportStandardPriorityPriority
Build vs buy

Why not build webhook replay in-house?

Writing a quick consumer on SQS or Redis is easy. Maintaining dead-letter queues, manual inspection UIs, payload retention, and safe one-click replay across dozens of providers is a perpetual engineering tax.

Building in-house
  • 3–4 weeks of engineering time to build ingestion, storage, and worker logic.
  • Ongoing cloud cost: $150–$600/mo for message brokers, compute, and database storage.
  • No visual inspection: developers grep through raw logs and manually craft curl scripts to replay events.
  • Maintenance tax: team handles worker restarts, schema migrations, and edge-case payload parsing.
With HookWatch
  • 5 minutes setup: point provider webhook URL to HookWatch, forward to your service.
  • Zero infrastructure to run: no queues to provision, no workers to scale, no database tables to vacuum.
  • Full visibility: exact headers, body, 500 error responses, and safe one-click manual replay.
  • Developer tooling: CLI tunnel for local dev and native MCP tools for AI coding assistants.
FAQ

Common questions.

Can I use this with Stripe?
Yes — HookWatch works with any provider that sends HTTP webhooks, including Stripe, GitHub, Telegram, Shopify, and Paddle. Point the provider’s webhook URL at your HookWatch endpoint URL.
Do you store webhook payloads?
Yes, so you can inspect and replay them. Payloads and delivery history are scoped to your workspace and only visible to its members.
Can I replay failed webhooks?
Yes — replay re-sends the exact captured payload to your endpoint once you’ve fixed the bug. Available today at no cost, on every tier.
Is billing live?
Yes — paid tiers are purchasable now through Paddle checkout. The Free tier stays free and needs no card to start.
Is this ready for production?
It’s early beta software. Capture, inspect, and replay are in daily use, but treat pricing, limits, and SLAs as not yet final.
Get started

Start free while HookWatch is in beta.

Create a workspace, capture your first webhook, and replay a failure — no card required.