Acknowledge
The alert is handled. The loop closes. A small receipt stays in your history.
Your infra,
reaching out.
The notification layer for what you run. Backups, cron, self-hosted services — they check in with your phone, not the other way around.
on the list · we'll write once, when it opens.
No launch date. No spam. One email, when it's ready.
Three actions. Everything else is scaffolding.
Snooze
Quiet for a window. Same alert, later, once. No repeats, no lost thread.
Resolve
Mark it finished. The flap goes quiet; the real one goes into history.
the surface
Designed for the moment you actually look.
You're not opening a dashboard. You're glancing at your phone between things. Every action is one tap — acknowledge, snooze, or resolve without unlocking.
Four steps. No glue code after the first webhook.
- 01 Your monitor fires a webhook.Uptime Kuma, Grafana, Healthchecks, Home Assistant, anything that can POST.
- 02 ackpoint dedupes and routes.Forty "disk full" events collapse into one. It lands on your phone.
- 03 A notification arrives.Tap to acknowledge, long-press to snooze, resolve when it's handled.
- 04 Your history keeps the receipt.Acknowledged at 11:24. The alert stops repeating. You go back to what you were doing.
Your alerts, yours.
Two modes. Described honestly — one shipping, one promised.
Zero-knowledge storage.
Your alerts are encrypted before they're stored, using a key that lives on your phone. The database, the backups, the logs — all hold ciphertext only. Plaintext exists in the routing path for milliseconds. Never at rest.
End-to-end encryption.
From your source to your phone, using the ackpoint binary. The server receives ciphertext directly; no plaintext crosses it, ever. Shipping with the Pro tier.
The point where alerts get acknowledged.
Said less. Meant more.
We'll write once, when it's ready.
No beta updates, no drip campaign. Leave your address; we'll email you the day it opens.
on the list · we'll write once, when it opens.