The worst way to learn your product is down is from a customer
Every team that has shipped something real knows the feeling: a quiet Tuesday, a Slack message from a customer, and the slow dread of realizing it had been broken for hours. The health check was green the whole time. The endpoint returned 200. It just returned the wrong thing.
That’s the gap most monitoring leaves open. A status code tells you the server answered — not that checkout completed, that the right rows came back, or that the page rendered without an error banner. We built Sentinel because catching the obvious outages was never the hard part. Catching the subtle ones was.
So Sentinel watches every layer — HTTP, Postgres, Redis, custom flows over SSH — and lets you decide what “healthy” actually means: with declarative rules, with sandboxed code, or with a model that reads a response the way a human would. Then it does the unglamorous, essential work: opens the incident, pages the right channel, tracks the SLA, and shows your customers a status page they can trust.
Know before your users do. Everything we build serves that one sentence.