§ concepts — pulse
what's a pulse?
A pulse is a heartbeat monitor. Instead of us reaching out to your service, your service reaches out to niceuptime — a quick check-in every time a job runs. Miss the check-in, and the missing run is recorded in the monitor evidence.
pulse — you check in
For things that run on a schedule: cron jobs, backups, queue workers, ETL. Silence is the signal.
probe — we check you
For things that should always answer over HTTP or HTTPS: websites, APIs, and health endpoints.
how it works
Create a pulse and copy its unique check-in URL.
Call that URL at the end of your job — one line of curl.
No check-in arrives in time? The missed run is recorded.
try the stateless demo
send a safe Pulse-shaped request
curl -fsS "https://example.niceuptime.com/pulse/nightly-backup-$(date +%s)"{"accepted":true,"demo":true,"stored":false,"example_id":"nightly-backup-1722864000","message":"Demo Pulse received. No monitor, API call, or database write occurred."}Use any valid example ID. The timestamp in a copied command makes each demo request feel unique.
The demo validates the request, but it does not create a Heartbeat, store monitoring data, or contact a real monitor.
A real Pulse uses a private monitor token, accepts a status payload, appends Heartbeat evidence, and can drive missed, degraded, or down state and an Incident.
ready to add one?
Set it up from one small form. No agent to install.
§ concepts — probe
what's a probe?
A probe is an outbound HTTP/HTTPS monitor. We call your website, API, or health URL on a schedule, then check that the response status is the one you expected. Bad status, timeout, or latency drift? The run is recorded for review.
probe — we check you
For things that should always answer over HTTP or HTTPS: websites, APIs, and health endpoints.
pulse — you check in
For things that run only sometimes: cron jobs, backups, queue workers, and ETL.
how it works
Create a probe and add the URL or endpoint we should check.
Choose the expected HTTP status and timeout for the runner.
The response drifts or disappears? The failed run is recorded for review.
live example Probe
no monitor · no evidence# run a real example Probe
GET https://example.niceuptime.com/health
expect status 200 within 10sexample Probe result
read-only previewheaders
body · application/json
checks
This was a live browser demo. No monitor or evidence was saved.
A real niceuptime Probe runs from configured regions, records Heartbeat evidence, evaluates saved response assertions, and can drive monitor state and Incidents.
ready to add one?
Point it at a URL, choose what good looks like, and let it watch.