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

smee.io review

Free#31 of 32 in Webhook Testing Software

An open-source relay for inspecting and forwarding GitHub webhooks locally.

6.0/10Editor score
smee.io6.0 Visit smee.io

Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026

smee.io is an open-source webhook payload delivery service for development and testing. It creates public channel URLs that external senders can call, shows incoming payloads in a browser, and delivers events to connected clients through Server-Sent Events. The smee-client CLI and Node client forward those deliveries to a locally running or external application. Its stated fit is solo developers and small teams working with GitHub webhooks and Probot integrations.

The workflow is focused and direct: create a channel, point a webhook sender at its public URL, inspect requests in the browser, and forward them through smee-client. GitHub and Probot are the listed integrations, while web access and self-hosted deployment cover the main platform choices. Teams can run the server as a Node.js application or Docker container, and an optional Redis message bus supports deployments with multiple instances. This makes smee.io suitable for local development workflows that need a reachable endpoint without exposing an application directly.

Security boundaries define where smee.io belongs. Channels are unauthenticated, so the project is intended for development rather than production use. Payloads are not stored server-side, although viewed payloads may persist in browser localStorage. The service therefore fits temporary inspection and forwarding of development events, not authenticated production ingress or workflows that require durable server-side payload storage. Choose smee.io when open-source control, local forwarding, and a simple browser view matter; choose another webhook platform when production authentication and operational safeguards are central requirements.

smee.io pros and cons

  • Where it wins
    • Creates public webhook channels for external senders
    • Browser inspection with Server-Sent Events delivery
    • Self-hosting via Node.js or Docker, with optional Redis
  • Where it doesn't
    • Unauthenticated channels are unsuitable for production traffic
    • Browser localStorage may persist viewed payloads
    • Requires an actively connected client for event delivery

smee.io 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