Hook vs Bark
Hook vs Hookdeck Console
Hook vs
webhook.siteA webhook.site alternative that taps you on the shoulder.
webhook.site is a browser tool for inspecting requests sent to a disposable URL. Hook does the inspecting too, but on a permanent endpoint that notifies your iPhone, so you don't have to keep a tab open.
Hook and webhook.site, side by side.
Hook Free, Pro from $5.99 a month | webhook.site Free URLs for 7 days; paid from $9 a month | |
|---|---|---|
| Price | ||
| Price | Free: 10 requests a month. Pro: $1.99/week, $5.99/month or $39.99/year; Lifetime $59.99 (US App Store prices) | Free; Basic $9/month, Pro $19/month |
| Volume | 10,000 requests a month on Pro | Free: 50 requests per URL; paid history from 1,000 requests |
| Receiving | ||
| Third-party webhooks | Yes: Any request from any service: point Stripe, GitHub or anything else straight at it | Yes: Any request |
| Read the full request | Yes: Headers, query string and full body, formatted, with the raw request kept | Yes: Headers, query and body |
| Signed payloads | Yes: JWS/JWT bodies decoded, nested ones too (App Store notifications) | No: Not listed |
| Sender recognition | Yes: Stripe, GitHub, Slack, Shopify, GitLab, Linear, Vercel, Sentry, Discord and the App Store named on arrival | No: Not listed |
| Email in | Yes: A mail.gethook.app address per workspace | Yes: An email address per URL |
| Forward to your service | Partly: Proxy to your own URL on Pro | Yes: Forwarding with retries, workflows and a CLI tunnel |
| Notifications | ||
| AI-written notifications | Yes: Title and summary written from any payload, in your language; or your own template | No: Not listed |
| Push | Yes: iPhone push, and browser push on Pro | No: No phone push |
| Publish from scripts | Yes: Hook-Title, Hook-Priority, Hook-Tags, Hook-Click, actions, as headers or URL parameters | No: No |
| Priority | Yes: Five levels, from silent (1) to urgent (5) | No: No |
| Platform | ||
| Apps | Partly: iPhone and iPad app, plus a web app; no Android | Partly: Web and a CLI; no mobile app |
| History | 7 days on Free; full history on Pro | Free URLs expire after 7 days |
| Self-hosting | No: Hosted only | Not stated on their pricing page |
| Open source | No: Closed source | Not stated on their pricing page |
- Supported
- Limited
- Not available
webhook.site details are from their public website and docs as of October 2026. Hook prices are US App Store prices.
Why people pick Hook over webhook.site.
It finds you
Every request is a push on your iPhone, so a webhook firing at 3 a.m. is not missed in a closed tab.
A URL that stays
Your endpoint doesn't expire, and Pro keeps the history.
Signed payloads made readable
App Store notifications and other JWS bodies open decoded.
When webhook.site is the better choice.
You need custom responses, workflows or a CLI tunnel to localhost.
You only test briefly in the browser and want it free.
You need CSV export or long retention on a team plan.
Questions about Hook and webhook.site.
Can Hook return a custom response like webhook.site?
No. Hook always answers 202 Accepted; use the proxy to pass requests to your own service if the sender needs a specific reply.
Can I try Hook without installing anything?
Yes. The homepage has a live endpoint that keeps requests for 15 minutes, no signup needed.
More in the docs: Get started · Publishing messages
How Hook compares with other tools.
- vs
ntfy alternative for iPhone
ntfy is an open-source pub/sub service: you publish a message to a topic and subscribed devices get it. Hook gives you an endpoint any service can call as it is, and shows the whole request as well as the notification.
Compare - vs
Pushover alternative
Pushover is a reliable push API: your code sends a token, a user key and a message. Hook is an endpoint other services call directly, so a webhook you don't control still becomes a notification you can read in full.
Compare - vs
Pushcut alternative for webhooks
Pushcut is built around iOS Shortcuts: notifications that run automations on your phone. Hook is built around the request: any service calls your endpoint and you read exactly what it sent.
Compare