About Yawpr

Yawpr exists because Slack notifications are not an alerting system.

The Problem

Your team mutes Slack. They have to — between bot notifications, thread replies, channel noise, and cross-timezone chatter, keeping notifications on all day is a productivity killer. So they turn them off. Set a schedule. Enable Do Not Disturb.

And then production goes down at 2 AM and nobody sees the message in #incidents until the morning standup.

The problem isn't your team. The problem is using a chat tool as a pager. Slack is great for conversations. It's terrible for "wake up right now, something is broken."

The Solution

Yawpr adds a dedicated alerting layer on top of your existing workflow. When someone types /yawp fire @backend in Slack — or when CloudWatch detects an anomaly — Yawpr routes the incident to whoever is on-call and hits them through channels they can't ignore:

• Push notifications that bypass DND — via ntfy.sh, fire-severity alerts arrive at max priority. Your phone vibrates even in silent mode.
• Slack DMs with action buttons — if Slack is open, you can acknowledge and resolve without leaving the app.
• A web dashboard — for when you need the full picture: timeline, comments, who's on-call, what's still active.

How It's Different

Existing tools like PagerDuty and Opsgenie are built for large enterprises with complex escalation policies and six-figure contracts. Yawpr is built for the team that just needs their on-call engineer to wake up when the database is down.

Set up takes two minutes. There's a free tier that covers most small teams. And because it runs on Cloudflare's edge network, alerts are delivered globally in milliseconds.

Built With

Cloudflare Workers, Hono, Drizzle ORM, D1, and Cloudflare Queues. No cold starts, no servers to manage, no single point of failure.