Hookfire: push notifications for every webhook your stack fires
Connect 30+ services including Stripe, GitHub, Sentry and Shopify, and get the events that matter as a notification on your phone, seconds after they happen.
- Know the instant you get paid
- Deploys, errors, and support pings
- No backend, no dashboard to babysit
More on hookfire.app:Feature tourEvery integrationHow it compares
Most of the important things that happen to a small software business happen while nobody is looking at a dashboard. A customer subscribes at 11pm. A deploy fails on a Sunday. An error starts repeating for every user on the signup page. The information exists. It is sitting in a webhook that some service is happily posting into the void, and nothing is carrying it to you.
Hookfire is the missing carrier. You connect a service, pick the events you care about, and Hookfire delivers them as a push notification on your phone. There is no server to run, no queue to keep alive, and no dashboard you are obliged to check. If nothing happens, your phone stays quiet.
It is the alerting half of the Releasy Suite: the part that tells you what your product just did, while Upvoted tells you what your users want next and Indie Polls tells you what they think.
How Hookfire works
Three steps, and the longest one is deciding which events you actually want to be interrupted for.
1. Connect a source
Pick a service from the integration list and follow the short setup, which is usually pasting a URL into that service's webhook settings, or authorising Hookfire directly. Most integrations take under five minutes and none of them require you to deploy anything.
2. Choose the events that matter
Every source ships with its event catalogue already mapped, so you tick the ones worth a buzz: payment succeeded, subscription cancelled, build failed, new issue, order placed. Nothing is switched on until you tick it, because an alerting tool that cries wolf gets muted within a week.
3. Get it on your phone
Install the Hookfire app, sign in with the same account, and events arrive as native push notifications with the detail already in the title: the amount, the customer, the branch, the error. Most of the time you never need to open anything. Push works on every plan; on Max the same event can also go out by email or into a Slack, Discord or Microsoft Teams channel.
What you can connect
More than 30 integrations, grouped by the kind of question they answer. Anything not on the list can be described as your own custom source on the Max plan.
Payments and billing
Stripe, Paddle, Lemon Squeezy, PayPal and Shopify. New subscriptions, one-off payments, failed charges, refunds and cancellations: the numbers that decide whether this month worked.
Code and deploys
GitHub, GitLab, Bitbucket, Vercel and Cloudflare. Pull requests opened, reviews requested, builds broken, deploys shipped. Useful precisely on the days you are not at a laptop.
Errors and alerts
Sentry issues, error events, and the issue and metric alerts your rules already fire, each one linking straight back to Sentry. A new exception class reaches you at the speed of a text message rather than the speed of your next email check.
Support, sales and anything else
Intercom, Crisp, Zendesk, Help Scout and tawk.to for support, Postmark and Resend for email, Clerk for signups. On the Max plan you can describe your own app as a source, and its events render like any built-in one. Max also lets you rewrite the title, body and link of any built-in event, so an alert reads in your words rather than the vendor's.
Deciding what is worth an interruption
An alerting tool earns its place by staying quiet. Most of what follows exists to keep the number of notifications you get in a day close to the number worth reading.
Filter on the payload, on Max
A rule reads the event itself, so you can take the payments over a hundred and ignore the rest, or watch one repository out of thirty. Twelve operators, from equals and contains through to present and blank.
Say how urgent it is, on Max
Every event gets a level: low, normal, high or critical. A critical alert keeps asking, every five minutes and up to six times, until somebody acknowledges it. That is the difference between a notification and a pager.
Quiet hours, snooze and mute
Set the hours nothing may wake you, snooze everything for an afternoon, or mute the one noisy integration and leave the rest alone. Included on Pro as well as Max, because a store that trades overnight would otherwise make the app unusable by Tuesday.
Spike protection, on Max
A cap on how many events an hour a single integration may interrupt anyone for, so the day a webhook goes into a loop is not the day you stop trusting your phone.
When you need more than the buzz
Every delivery is recorded, which is what makes the rest of this possible. These are the operator's tools, and they are on Max.
Replay a delivery
Send a recorded delivery through again to check a fix, or to get back an alert that arrived while your phone was face down on a table somewhere.
Hear when a source goes quiet
Hookfire watches for the integration that was delivering and has stopped. It is the failure nobody notices, because its only symptom is silence.
Forward the webhook on, signed
Pass the verified event to your own endpoint, signed with HMAC-SHA256 over the timestamp and the body, so your server can trust it without you implementing a different verification for every vendor.
See what actually arrived
Success rate, latency and volume per integration, with unlimited history and CSV export, so a question about a delivery has an answer rather than a guess.
Why not just use email, or Slack
Both work, and both are where alerts go to die. Email arrives in the same inbox as newsletters and invoices, so it competes with noise you have already trained yourself to skim. A Slack channel is better, until it becomes a firehose nobody reads and someone mutes it.
A notification is a different medium
A push notification is short, it is on the device already in your hand, and it is disposable. That combination is what makes it survivable at volume: you read it in a second and it is gone, instead of accumulating into a backlog.
Nothing to build, nothing to maintain
The do-it-yourself version of Hookfire is a small server, a queue, retry logic, a push certificate, and a device token store. It is a weekend to build and then a thing you own forever. Hookfire is the version where none of that is yours.
Who Hookfire is for
- Solo founders
- You are the ops team. Hookfire is the pager that does not require you to run a pager.
- Small product teams
- Share sources across the team: two seats on Pro who both see everything, or on Max as many people as you like, with each event going to whoever is on support this week.
- Agencies and freelancers
- Watch client projects (deploys, form submissions, failed payments) without logging into five dashboards.
- Anyone with a side project
- The first sale of a new product is a moment. Hookfire makes sure you are not the last to find out about it.
Hookfire comes with two more tools
is one subscription covering all three apps, on one login and one bill. Buy it inside any of them and the other two unlock on the same account.
Feature voting from your users
A public board where users post ideas and vote, so you build what people actually want, not the loudest email.
About Upvoted
Answers, embedded anywhere
Lightning-fast surveys you drop in with one snippet. Nine kinds of question, live results, real answers.
About Indie PollsHookfire FAQ
What is Hookfire?
Hookfire is a notification service that connects to 30+ tools you already run, including Stripe, GitHub, Sentry and Shopify, and delivers their webhook events to your phone as push notifications, seconds after they fire.
Do I need to write any code to use Hookfire?
No. For supported services, setup is either an OAuth authorisation or pasting a Hookfire URL into that service's webhook settings. To send events from your own application you describe it once as a custom source, which is a Max feature, and then POST to the URL that gives you.
Which services does Hookfire support?
More than 30 integrations across payments and billing (Stripe, Paddle, Lemon Squeezy, PayPal, Braintree, Square, Chargebee, Recurly), ecommerce (Shopify, WooCommerce, BigCommerce, Magento), code and deploys (GitHub, GitLab, Bitbucket, Vercel, Cloudflare), errors (Sentry), support (Zendesk, Intercom, Help Scout, Crisp) and email (Postmark, Resend), plus custom sources you define yourself on the Max plan.
Will Hookfire flood my phone with notifications?
Only if you ask it to. A new integration sends nothing at all until you pick the events worth a notification, so a high-volume event only reaches you if you chose it. Quiet hours, snooze and mute are there on Pro and Max, and Max adds payload filters and an hourly cap per integration. The intent is a handful of meaningful alerts a day, not a live feed.
Can alerts go somewhere other than my phone?
On Max, yes. The same event can be delivered by email or posted into a Slack, Discord or Microsoft Teams channel, and Max can also forward the verified webhook to your own endpoint, signed with HMAC-SHA256. Push notifications and the web inbox are on every plan.
How much does Hookfire cost?
Hookfire is included in the Releasy Suite at $69 a month, which also unlocks Upvoted and Indie Polls on the same account and the same bill. Hookfire also sells standalone plans on its own site if you only want the alerts: Pro at $19 a month or $190 a year, and Max at $39 a month or $390 a year.
Can I try Hookfire before paying?
Yes. The Releasy Suite starts with a 7-day free trial with every app unlocked and no card required, and you can cancel in a click.
Get Hookfire with the whole suite
$69 a month for Hookfire, Upvoted and Indie Polls, each on its Max plan. 7-day free trial, no card, cancel anytime.