chegou vs Webhook Notifier

chegou (Portuguese for "it arrived") is the simplest way to get push notifications on your phone. No account. No dashboard. No configuration portal. Just a webhook URL. Install the app, copy your unique URL, and paste it into your scripts, CI/CD pipelines, cron jobs, monitoring tools — anything that can make an HTTP request. When it fires, your phone buzzes. That's it. • One URL, infinite use cases — deploy alerts, server monitoring, CI results, reminders, whatever • Channels — group notifications by purpose (deploys, monitoring, ci, personal) • Scheduled delivery — send now, deliver later (up to 24 hours) • Custom sounds — 13 built-in sounds from meow to microwave • Action buttons — add tappable buttons that open URLs • Image support — attach images to your notifications • On-device history — all notifications stored locally, nothing on our servers • Multi-device — pair multiple devices with a QR code Free forever. Or at least until the server bill gets weird. No analytics. No tracking. No ads. We don't even know your name. Built by a developer, for developers. chegou.dev

Webhook Notifier is an alert app for engineers and operators. Point any system that can send an HTTP request at a URL the app gives you. When the URL is hit, your phone rings. Rules per webhook. Match by HTTP method, by header, or by substring or regex in the body. Alerts only fire when the request actually means something to you. Quiet hours per webhook. Pick the days and the time window when each webhook may wake you. Outside the window the alert is dropped silently. No buzz. No missed call. Bypass silent per webhook. For the alerts that genuinely cannot wait, like production outages or water leak alarms, flip the switch and the notification rings through Silent and Focus modes. This requires the Critical Alerts entitlement from Apple. Share read only. Hand the secret to a teammate and they receive every alert too. Rotate the secret when you want to revoke that. No tracking. No advertising. No analytics on the content of your webhooks. The bearer token that authenticates your device is generated on the device and only the hash is stored on the server. Built for people who already know what a webhook is.