Hookspot and smee.io compared
Choose Hookspot to keep webhooks for 14 days on Free and retry them when you're ready. Choose smee.io to receive webhooks without an account while a client is running.
Free for 25,000 deliveries a month. No card needed.
| Hookspot | smee.io | |
|---|---|---|
| Price | $0 on Free. Pro is a flat $19 a month, or $190 a year. | $0, with no account |
| Free plan | 25,000 deliveries a month. At that limit, your projects lock until you upgrade or the month ends. | No account and no plans |
| History kept | 14 days on Free, 60 days on Pro | None on the server. The channel page keeps what it showed in your browser. |
| Members | 3 on Free, 25 on Pro | No accounts. Anyone with the channel URL can see the payloads sent to it. |
| How it reaches your app | hookspot listen forwards each delivery to the app on your laptop. | A channel URL that streams each payload to smee-client. |
| While the CLI is off | Stores each webhook. Its delivery waits as Skipped until you start the CLI and click Retry. | Payloads go only to connected clients, the channel page included. With none connected, the webhook is gone. |
| Delivery to production | No. Hookspot delivers only to the app on your laptop. | No. smee.io is for development only. |
Checked 8 October 2026 against smee.io's README, GitHub's testing guide and Probot's development docs.
Webhooks wait while the CLI is off
smee.io sends each payload to connected clients and stores none on its server, as its README explains. If no client is connected, including the channel page in a browser, it cannot save the webhook for later.
Hookspot stores each webhook first. While hookspot listen is off, its delivery waits as Skipped, for 14 days on Free and 60 on Pro. Start the CLI and click Retry.
Return to the request and its response
Hookspot keeps the request's headers and body alongside each delivery attempt and your app's response. Other members of your organization can inspect the same history.
The smee.io channel page saves payloads in your browser while it is open and lets you send one again.
Inspect the requestWhen to choose smee.io
- You want to receive webhooks for free without creating an account. Open smee.io and you get a channel URL.
- The guide you follow already uses it, as GitHub's testing guide and Probot's docs do.
- You want to run your own server. smee.io is a small Node.js app you can deploy yourself.
Switching from smee.io
Create a route
Create a free account and name your organization. Then name a source and choose a path in your app, such as
/webhooks/orders.Update your webhook URL
Copy the source's webhook URL from Hookspot. In the service that sends your webhooks, replace your smee.io channel URL with this URL.
Run
hookspot listenWith Node.js 18 or newer and your app on port 3000, run these commands in any directory instead of
smee. Approve the login in your browser.
Follow the quickstartnpm install -g @hookspot/clihookspot loginhookspot listen --forward-to http://localhost:3000
Send your first webhook to your laptop.
Install the CLI with npm (Node.js 18 or newer) or Homebrew.
Hookdeck, webhook.site and smee.io belong to their owners; their facts come from their public pages, checked 8 October 2026.