Back to SensaCat

About SensaCat

SensaCat is a monitoring platform for the failures that leave every server green: a cron job that quietly stopped running, a webhook that never arrived, a business process that stalled halfway, an API credential about to expire over a weekend.

Why it exists

Infrastructure monitoring answers one question well: is the machine up? It is very bad at the question that actually costs money, which is whether the work got done.

A payment can be captured while the fulfilment webhook never fires. A nightly export can be switched off by a deploy and nobody finds out until a customer asks for a report. A certificate expires on a Saturday. In each case the dashboards stay green, the error rate stays at zero, and the first alert is an email from a customer.

SensaCat exists to make silence itself the alert. You describe what should happen and how long it may take, and you hear about it when that stops being true.

What it watches

  • Heartbeat monitors — cron jobs, queue workers and scheduled tasks check in on an interval. Miss the window and the job shows as late; miss the grace period too and it raises an alert.
  • Business flows — multi-step processes such as checkout to fulfilment or sign-up to onboarding. Each step has a maximum gap, and an instance that outlives its next step's gap is reported as stalled.
  • Credentials — API keys, tokens and certificates, with reminders that start as warnings and turn critical as the expiry date approaches.
  • Domains — registration expiry, SSL certificate expiry, and uptime probing with two consecutive failures required before anything is raised.

Alerts fan out to email, Slack, Discord, SMS and phone calls, and escalate when nobody acknowledges them.

How it is built

A few decisions we are not planning to reverse:

  • One alert per incident. A stalled flow or a silent job raises a single alert when it breaks, not a fresh one on every check. Monitoring you learn to ignore is not monitoring.
  • Nothing to install. No agent and no SDK. Sending an event is an HTTP POST, authenticated with the resource's own ingest token and your account API key, so a leaked URL on its own cannot write data.
  • Metadata only. An event carries timestamps, the flow or monitor it belongs to, the id of the record moving through it and a status. We do not ask for payload contents and do not store them.
  • Late is not down. A job that runs a little behind schedule is shown as late on the dashboard and wakes nobody. A 4xx from a domain is treated as up, because bot protection refusing a checker is not an outage.

Who runs it

Tabrosh Shaikh

Solo founder & Lead Software Engineer

Solo founder and lead software engineer, with 11+ years building SaaS products, APIs and web applications.

Currently building SensaCat — a simple way to monitor revenue-critical integrations, webhooks, APIs and automations before silent failures turn into expensive problems.

SensaCat is independently funded and built by one person. It is not venture-backed, it has no sales team, and the person who answers support is the person who writes the code.

That shapes what you can expect: the pricing page shows the real limits rather than "contact us", the free plan is a real plan rather than a trial, and a feature that is not built yet is not listed as if it were.

You can check both claims without asking anyone. The changelog lists every release with the date it shipped, and the status page reports what the system is doing right now, measured rather than asserted.

Why I built it

Eleven years of building SaaS products, APIs and integrations taught me which failures actually cost money, and it is almost never the ones that page you. It is the integration that quietly stopped firing. The webhook the provider retried three times and then gave up on. The automation that has been throwing away every third record since a deploy six weeks ago.

Every one of those had monitoring in front of it. Uptime checks were green, error rates were zero, and nothing was down — because nothing was down. The work simply stopped happening, and no tool I had was watching for the absence of something.

Each time, the same two things were true: we found out from a customer, and the fix took minutes once we knew. The expensive part was the gap in between, and that gap was measured in days.

SensaCat is the tool I wanted during those weeks. You tell it what should happen and how long it may take. When that stops being true, it tells you — before the invoice, the refund or the apology email.

Talk to us

Questions about the product, pricing, security or anything else go to [email protected], or through the contact form. Bug reports and feature requests are welcome at the same address.

If you want to try it, the pricing is public and 20 free tools need no account at all.