Feature

Heartbeat & metric monitors

Uptime checks cover what the internet can reach. The nightly backup, the queue worker, the billing cron job: those fail silently. Service monitors flip the direction. Your systems report in to Xpiry, and you hear about it the moment they stop.

Two kinds of monitor

Heartbeat

Expects a ping on a schedule. Tell Xpiry how often the job runs and how much grace to allow. A missed window flips the monitor to down and alerts you. Optionally flag runs that finish but take too long.

Metric

Watches a number you push. Queue depth, p95 latency, error counts. Each ping carries a value, compared against your warn and critical thresholds in whichever direction is bad for that metric.

One line of curl

Each monitor gets a tokenized ingest URL. Append it to a cron job, a deploy script, or a worker loop, authenticated with one of your API keys:

# heartbeat: report a successful run

curl -H "Authorization: Bearer $XPIRY_API_KEY" https://xpiry.dev/ping/<token>

# report a failure explicitly

curl -H "Authorization: Bearer $XPIRY_API_KEY" https://xpiry.dev/ping/<token>/fail

# metric: push a value

curl -H "Authorization: Bearer $XPIRY_API_KEY" "https://xpiry.dev/ping/<token>?value=42"

Wired into everything else

› Down and degraded states alert on your configured channels, and re-fire until acknowledged or recovered
› Monitors can appear on your public status page, grouped into named components
› Every ping is kept as history, so you can see exactly when a job started misbehaving

Availability

Service monitors are on every plan, differing only by per-domain limit: 1 on Free, 3 on Hobby, 5 on Pro, 20 on Agency.

Start monitoring in minutes

Free for one domain. No credit card required.

Get started free

See the full feature list or pricing.