Hesklo watches your sites, APIs and infrastructure. When a check fails, it runs the escalation policy your team designed — routing the incident to the right person, at the right hour, through the tools you already use.
One monitor, one policy — from the first failed check to the all‑clear, without anyone watching a dashboard.
Most teams run monitoring in one tool and on-call in another, then glue them together. Hesklo owns the whole path, so there is one place to look when something breaks and one place to change what happens next time.
Checks run on their own interval from our infrastructure. A failure is confirmed over several consecutive runs before it counts as an outage.
The monitor hands off to the escalation policy you designed: branch on state, wait for duration, gate on hours, repeat until acknowledged.
Each step delivers to a named destination — a channel, an engineer, the on-call rota, or an incident in PagerDuty.
Recovery closes the loop automatically: incidents and tickets resolve on the same key, and the outage is written to history.
Point Hesklo at anything that answers. Each monitor runs on its own interval and confirms a failure across consecutive checks before it counts as an outage.
Match an exact status code or accept any 2xx, and optionally require a string in the response body. SSL certificate expiry is tracked on every HTTPS check.
A plain ICMP check for whether a machine answers at all — the simplest signal that a host is alive.
Open a connection to a host and port to confirm a database, cache or service is accepting connections, without issuing a full request.
Connect over SSH and run one of a fixed set of read-only diagnostics: service active, disk usage, memory usage or load average. Chosen from a list, so there is nothing to inject.
An escalation policy is a set of connected nodes, not a configuration file. Draw a path from the monitor's down port and it executes exactly as it reads — branch on state, hold for duration, gate on hours, repeat until someone acknowledges.
Route on monitor state: up, down, down longer than N minutes, just recovered, unacknowledged for N minutes, or a certificate expiring within N days.
Hold the steps that follow until the monitor has been continuously down for a set number of minutes. The basis of tiered escalation.
While the monitor stays down, re-run the steps after it on an interval. Keeps paging until someone acts; resets on recovery.
Only pass through during set hours and days, in your timezone. Overnight windows supported. Put noise behind it, keep the critical path open.
Run a live probe mid-flow — HTTP, ping, TCP or SSH — and take the pass or fail path from the result.
Call an endpoint to restart a service, scale a group or trigger a runbook. Once per incident, or on every check while down.
Configure a destination once, then reference it from any notify step in any policy. Every plan, including the free one, has all eight.
Post to a channel via an incoming webhook.
Post to a channel via an incoming webhook.
Post to a channel via a webhook.
Built in. Any team member, with an optional Acknowledge link.
Text a number through your own Twilio account.
Trigger an incident on the Events API. Resolves on recovery.
Open an issue in a project. Closes on recovery using the same key.
POST to any URL with an optional bearer token.
Team seats are included in the plan price on Team and Business. Nobody is billed per head, and nobody is left holding an alert that was never acknowledged.
Everyone signs in as themselves and works on the same monitors, connections and history. Nothing is configured twice, and access is revoked the moment a member is removed.
Paint a repeating week of shifts across the people on your account. Any Email step set to follow the rota pages whoever is on duty at the moment it fires.
Built, operated and hosted inside the European Union by Sverige Analytics AB, a registered Swedish company.
Read-only members see everything and change nothing. Full members build and edit. Billing stays with the account owner.
Every outage is recorded with its cause and duration, alongside per-monitor uptime and response-time charts and a full event log.
Pause a monitor for planned work so a known outage pages no one. History is kept and the monitor resumes as it was, optionally on a timer.
Publish selected monitors to a status page on your own subdomain, so customers and colleagues can check before they ask.
An optional Monday summary of how your monitors performed the previous week. Off until you turn it on.
All capabilities are on every plan. What changes is scale: how many monitors you run, how often they check, how far back history goes, and how many colleagues come along.
EUR · billed monthly · cancel any time · full comparison →
One thing you watch on one check — a single URL, host, port or SSH diagnostic. The number of escalation steps or destinations its policy uses makes no difference.
No. Every plan, including Free, has all eight destinations. The plan governs how many monitors you run and how often they check, not where alerts can go.
They are not. Team includes ten seats and Business twenty-five, in the plan price. There are no per-seat charges and no setup fees.
In the EU. Hesklo is built and hosted in Sweden and operated by Sverige Analytics AB, a registered Swedish company.
Three monitors and all eight destinations are free forever. Add a check, define what happens when it fails, and watch it run.