Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

Receptor review

Free#14 of 32 in Webhook Testing Software

A self-hosted webhook capture and replay server with broad integrations.

6.9/10Editor score
Receptor6.9 Visit Receptor

Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026

Receptor is an open-source, self-hosted webhook testing and inspection server written in Rust. It creates token-protected endpoints that capture HTTP requests and streams methods, paths, query parameters, headers, bodies, and responses to a browser UI. Captured requests can be inspected and replayed, making it suited to developers and teams that need control over webhook traffic. It runs on Linux, macOS, and Windows, with web and API access, and its company-size fit spans solo users through enterprise teams.

The central workflow combines live inspection with request replay. Server-sent events stream captured activity to the browser, while SQLite stores requests for later review. Receptor accepts arbitrary HTTP methods and subpaths, and an optional token-bucket rate limiter adds control over incoming traffic. Automatic retention keeps up to one week or 200 requests per endpoint. Integrations cover GitHub, Stripe, Shopify, Linear, Slack, GitLab, Bitbucket, Twilio, Mailgun, SendGrid, Notion, Plaid, Segment, Zapier, and n8n, giving it a wide ecosystem fit for common webhook sources and automation tools.

Deployment is deliberately self-managed: options include Docker, Kubernetes, or a standalone binary. The published product details describe an open-source distribution with a free plan, rather than paid tiers with different feature sets. Receptor does not provide mock endpoints, so teams that need synthetic webhook producers or endpoint simulation should choose a tool centered on mocking instead. It is a practical fit when capturing real requests, reviewing payload details, replaying deliveries, and retaining a bounded request history matter more than hosted operation or mock-server features.

Receptor pros and cons

  • Where it wins
    • Token-protected endpoints with live browser inspection
    • Request replay with SQLite storage and automatic retention
    • Docker, Kubernetes, standalone deployment and broad integrations
  • Where it doesn't
    • No mock endpoint support
    • Retention is limited to one week or 200 requests per endpoint
    • Self-hosted deployment with community and documentation support

Receptor fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update