READS WHAT YOUR TEAM ALREADY WROTE DOWN
Your own incident history becomes your on-call copilot.
When alerts storm, Kesvara groups them into one incident and searches your library for one that looks like it. If you have fixed it before, the action item somebody wrote at the time shows up quoted, dated and linked.
WEBHOOK OR FORWARDED EMAIL · NO AGENT TO INSTALL · NO MODEL PICKS A MATCH
It suggests from history. It does not diagnose. Every suggestion cites a prior incident by date, and when nothing in your library is close enough the screen says so rather than guessing.
Checkout latency
grafana ×14 · sentry ×9 · uptimerobot ×6 · postmark ×2 · window 14:02–14:09
- 14:02:41 grafana checkout p95 > 2s (warn → crit)
- 14:03:15 sentry PoolTimeout: all connections in use (×214)
- 14:04:02 uptimerobot /checkout 502 from 3 regions + 28 more, grouped
“Raise pool max to 200 and mirror it into the deploy checklist.”
incident #171 · what resolved it, as written at the time · platform
Open incident #171 →
Three steps, and the third one is the product
1 · Forward the alerts
Two doors. Each workspace gets a webhook URL to POST to — Alertmanager
and Grafana work as they are — and an address at
in.kesvara.deplyra.com for tools that only send email.
On this deployment nothing is receiving mail at in.kesvara.deplyra.com: the endpoint exists and is tested, and no mail routing points at it, so a forwarded alert is discarded before Kesvara sees it. The webhook is the door that works today.
2 · One card, not forty
Repeats of the same check collapse for two hours; different symptoms naming the same service collapse for twenty minutes. The rule that fired is printed on every alert, so you can disagree with it.
3 · Similar to 3 Mar
When an incident resembles one you have resolved, you get the earlier incident, its date, the words the two share, and the action item you wrote. If nothing is close, you get told nothing is close.
What it is not
Kesvara does not detect anything and will not wake anyone up. It sits downstream of the tool that pages you. It holds no shared corpus of other companies' outages: the library it searches is your own history and nothing else, so it is useless on your first day and useful on your fiftieth.
It will not tell you what broke. A tool that offered a cause from the text of an alert would be guessing, and a confident guess at 3am is worse than silence — you would chase it.
Pricing
Nothing is charged. There is no card form on this site and no paid plan behind it. If you want to know when there is one, leave an address.