Hesklo checks your sites and servers around the clock, then runs the escalation policy you draw yourself. Branch on how long something has been down, gate alerts to office hours, route them anywhere your team works, and send the all-clear automatically when a service recovers.
Drag a monitor onto the board and wire it to waits, branches, schedule gates and notify steps. The whole on-call policy reads at a glance instead of hiding in dropdowns and config files. What you see on the canvas is exactly what runs.
Watch a URL's status code and response body, a raw TCP port, or the exit code of a command run over SSH. Every check is agentless and runs as often as every 30 seconds, so there is nothing to install on the things you watch.
Route on whether a service is down, up, just recovered, or down longer than you are willing to tolerate. Page a human only when an outage is worth waking someone for, and let shorter blips pass quietly.
Every monitor has a recovery port. Hang a notify step off it and the all-clear sends itself the moment a service comes back healthy, with no second flow to maintain and no manual resolve step.
Gate alerts to office hours with a schedule block, and pause a monitor for planned work so a known outage never pages anyone. Maintenance windows keep your on-call signal clean during deploys and migrations.
Require several failed checks in a row before a monitor counts as down, so a single flaky response never drags you out of a meeting. Tune the threshold per monitor to match how noisy each target is.
Route notifications to Slack, Discord, Microsoft Teams, email, SMS, PagerDuty, Jira and any webhook. Set up a connection once, then point any notify step at it. Every integration is available on every plan, including Free.
Each notify step fires at most once per incident and resets on recovery, so a long outage never buries your team under repeated pages. One incident means one alert, not one alert every check interval.
Publish a hosted status page on your own subdomain so customers can check service health without opening a ticket. Uptime history and current incidents update straight from your monitors.
Watch live status and uptime over your plan's retention window on a single overview, with per-monitor history drawn from the same check results. See at a glance what is healthy and what has been flapping.
Integration tokens and SSH credentials are encrypted at rest, and monitors, connections and history are scoped to your account. Your alerting data belongs to you and is never shared across tenants.
Hesklo probes your services from the outside over standard protocols, so there is no agent to deploy, patch or trust on your own boxes. You go from a blank canvas to a running escalation policy in minutes.
Hesklo checks HTTP and HTTPS endpoints (status code and response body), raw TCP ports, and the exit code of commands run over SSH. Checks are agentless and run as often as every 30 seconds.
You draw the policy on a canvas. A monitor has a down port and an up port, and you wire waits, if/else branches, schedule gates and notify steps off them. The flow you see is exactly the flow that runs when a check fails or recovers.
Slack, Discord, Microsoft Teams, email, SMS, PagerDuty, Jira and webhooks. You configure a connection once and point any notify step at it. Every integration is available on every plan, including Free.
No. Each notify step fires at most once per incident and resets on recovery, so one incident means one page rather than one page every check interval.
Yes. Pause a monitor for planned work so a known outage never pages anyone, and use a schedule gate to restrict alerts to office hours.
Yes, and they are free on every plan. Wire a notify step to a monitor's up port and the all-clear sends itself the moment the service is healthy again.
Add a monitor, wire up the flow, and let Hesklo handle the 3 a.m. part.
Open the dashboard