Docs

Create a monitor and send your first ping in two minutes.

Every URL a heartbeat monitor understands: success, start, fail, exit codes, logs.

Wrap any command so its start, exit code, duration and output tail are reported.

Add a ping to a crontab line with curl, or wrap the job.

Report a systemd service run with ExecStartPre / ExecStartPost.

Ping from PowerShell and report failures with the exit code.

Know when a scheduled workflow stops running, not just when it fails.

Wrap the container command so every run reports.

Report container jobs and one-shot services.

A Schedule Trigger that stops firing produces no failed execution, so your Error Workflow never reports it. Here is the check that does.

Add an HTTP module as the last step of a scenario or zap.

requests, urllib, and a decorator that reports exceptions.

fetch, plus a wrapper for scheduled scripts.

net/http and a helper that reports panics and errors.

Let scheduled agents and hooks report that they ran, and alert when they go quiet.

Give Claude, Cursor or any MCP client tools to create monitors and check in.

Uptime checks with status codes, keywords, intervals and thresholds.

Email, webhooks, Slack, Discord, Telegram and ntfy, and the webhook payload.

Publish a public status page and embed SVG badges.

Create and manage monitors with an API key.