Features

Four monitor types, one alerting pipeline. Bundled with on-call and status pages so you don't have to wire it up yourself.

The dead-man's-switch your scheduler doesn't have

Cron heartbeats

Your job pings a unique URL when it runs. We hold a grace window after the expected time; if no ping arrives, we open an incident and route it through your alert channels.

Works with any scheduler — Linux cron, GitHub Actions, Kubernetes CronJobs, Airflow, Render cron, Fly machines. If it can curl, it can heartbeat.

  • Cron expressions or simple intervals
  • Configurable grace period per monitor
  • Captures the request body — see the last 10KB on the dashboard
  • /start, /fail, and /log variants for in-flight signals

HTTP, TCP, and TLS-cert from multiple regions

Uptime checks

Tell us a URL or host:port; our prober runs the check from each region you enable on a configurable cadence. Each region's result is recorded so you can see where it failed first.

Consensus-based alerting collapses one flaky region into noise instead of paging you. Set the threshold per monitor.

  • HTTP status, latency, and content-match assertions
  • TCP connect-success probes
  • TLS cert-expiry checks (alerts at 30 / 14 / 7 days)
  • Choose any subset of regions

The PagerDuty feature set, included

On-call schedules

Define rotations as layers — weekday primary, weekend secondary, monthly handoff — and we resolve who's on call for any incident at any moment. Overrides cover vacations and swaps without restructuring the rotation.

Escalation policies fire steps in order: page primary on SMS, then secondary, then notify the team Slack, with configurable waits between each step. Acks pause the chain without closing the incident.

  • Time-zone-aware schedule resolution
  • Email, SMS, Slack, and generic webhook channels
  • Per-incident ack via dashboard or webhook
  • Audit log of who was paged when

Public, edge-cached, on your domain

Status pages

Curate a subset of monitors into a public page at status.yourcompany.com. Visitors see current state, recent incidents, and (optionally) subscribe to email updates per page.

Pages are cached at the edge for a minute, so a viral incident won't melt your origin. Bring your own domain on the Pro tier.

  • Custom domain on Pro+
  • JSON API at /api/status/<slug> — embed anywhere
  • Hide individual monitors per page
  • Optional email subscriptions on Team

Ready to wire it up?

Five monitors free, no credit card. Upgrade when you outgrow it.