Something broke. Acked makes sure someone owns it.

Point your monitoring, your cron jobs, or a curl command at Acked. Define who's on call. Acked notifies them, retries if they don't respond, escalates if they still don't, and keeps a record of all of it.

That's the product.

Get early access Free for individuals · flat for teams · unlimited teammates

The problem

Your tools already know when something breaks. The hard part is making sure the right person sees it.

Acked checks who's on call, sends the notification, escalates when nobody responds, and keeps a record of what happened.

Your monitoring stays. Your Slack stays. Your process stays. Acked just makes sure someone gets the message.

How it works

Signal Acked right person notified confirmation

A signal comes in over HTTP. Acked checks the schedule, notifies whoever is on call, and keeps trying until a human acknowledges. Then it logs everything and gets out of the way.

Datadog · Grafana · GitHub · Cron · Your code · AI agents
acked
Slack · Push · Webhooks · Your tools

Scheduling

Who should know?

Rotations that handle time zones and vacations without a shared spreadsheet. Overrides for "I'm at a wedding Saturday, can you take my shift." Escalation chains for when the primary doesn't answer.

Nothing clever. A schedule that's correct at 3am is worth more than one with features.

Notifications

Did they actually find out?

An alert nobody saw is the same as no alert. Acked pushes to your phone first. No response? It retries. Still nothing? It moves down the escalation chain to the next person.

Delivery isn't done when the notification is sent. It's done when a human acknowledges it.

Reporting

What happened?

Every attempt is logged: which signal fired, who was notified, on what channel, at what time, and who acknowledged. When someone asks whether anyone got paged Saturday night, you have a record instead of a guess.

Integrations

How does everything connect?

HTTP in. HTTP out.

Anything that can make an HTTP request can get a human's attention. Datadog and Grafana work out of the box. So does a GitHub Action, a cron job, a bash script that exits nonzero, or an AI agent that needs human approval.

Pricing

Adding someone who can fix a problem should never increase your bill.

No per-seat pricing. Put the whole team on the schedule. Add the contractor. Add the founder who still takes pages. Your bill doesn't move.

Team tiers start at $49 a month, flat, sized by usage, with soft limits. If a rough month blows past your alert volume, we deliver the alerts and sort out billing afterward. We will never drop a page because of a plan threshold. That would defeat the entire point of the product.

Oh, and free for individuals.

Why we built this

On-call tooling grew into platforms. Incident timelines, AI summaries, service catalogs, retro workflows. That's fine for companies that need it. Many teams don't, so they end up either paying for a platform they use 5% of, or duct-taping alert emails to a shared inbox and hoping.

We built the piece that was actually missing: software that gets the right person's attention, reliably, and then gets out of the way.

Questions we'd ask too

No SMS or phone calls?

We do push and email because they're effective and easier to track: full context, an ack button, delivery receipts. Need voice? Let's talk.

What if you can't reach someone?

We escalate. No acknowledgement within your window and the next person in the chain is notified, until someone confirms. Every attempt is recorded.

Why not an incident management platform?

Not everybody needs one. Sometimes it's as simple as getting alerted and hopping on Slack. We're not here to force a process. We're here to support yours.

Acked owns delivery, not resolution.