Hesklo
Monitoring meets on-call

When something breaks, you already drew what happens next.

Hesklo watches your sites and servers. The moment one goes down, it runs the escalation policy you drew on a canvas. No YAML, no on-call tooling to wire together.

No credit card · One monitor free, forever
Watch
HTTP, ping, TCP or SSH
Decide
Your policy, drawn out
Notify
The right people, in order
What it watches

Four ways to ask "is it up?"

Point Hesklo at anything that answers. Each check runs on its own interval and confirms a real outage before it pages anyone.

  • HTTP
    Sites and APIs

    Match a status code, or require a string in the body. SSL expiry is tracked automatically.

  • PING
    Host reachability

    A plain ICMP check for whether a machine is answering at all.

  • TCP
    Open ports

    Confirm a database or service port is accepting connections.

  • SSH
    Run a command

    Exit zero is up. Check a service, disk, or anything a shell can answer.

The canvas

Drag the logic. Skip the config files.

An escalation policy is just nodes you connect. Drop a module, draw a line from the monitor's down port, and it runs exactly as it reads. These are the pieces you build with.

module

If / else branch

Route on whether the monitor is up, down, or how long it has been down.

module

Condition check

Probe something live and take the pass or fail path from the result.

module

Wait

Hold an escalation step until the monitor has been down long enough.

module

Repeat alert

Keep paging on an interval until someone acts. Resets on recovery.

module

Schedule gate

Only let alerts through during set hours and days, in your timezone.

module

HTTP action

Call an endpoint to restart, scale, or kick off a runbook.

Where alerts land

Notify wherever your team already is.

Connect a destination once, then reference it from any notify step. PagerDuty incidents and Jira tickets open on the way down and resolve on the way back up.

Slack
Discord
Teams
Email
SMS
PagerDuty
Jira
Webhook
The quieter details

Built so a real outage gets through, and nothing else does.

Flap dampening

A cooldown per notify step means a service bouncing up and down does not turn into a hundred messages.

Confirm before paging

Require several failed checks in a row before an outage counts, so the odd blip stays quiet.

Schedule gates

Hold non-urgent alerts to working hours and let the genuinely critical ones through any time.

Public status pages

Flip a monitor on to your own status page at a subdomain, so others can check before they ask.

SSL expiry tracking

Every HTTPS monitor counts down its certificate and warns you well before it lapses.

Incident history

Every outage is recorded with cause and duration, with uptime and response-time charts per monitor.

Weekly summary email

An optional Monday recap of how your monitors did the week before. Off by default.

Auto-resolve

PagerDuty and Jira close themselves on recovery using the same key, so nothing is left hanging.

Draw your first policy in a few minutes.

One monitor is free forever. Add a check, draw what happens when it fails, and see it run.