Uptime, workflow testing, and on-call paging

Every second, watched.

PulseChecker watches your endpoints, cron jobs, and AI agents — and tests the actual flows your users run, like login and checkout. The moment something breaks, you hear about it: email, text, or a phone call until someone answers.

URL checks
Heartbeat check-ins
Agent runs
Workflow tests
On-call paging

Start free

Features

Three ways to watch your systems

Ping any URL on a schedule, wait for a heartbeat check-in from your cron jobs, or watch an AI agent run end to end. However something runs, you find out the moment it goes quiet.

Ping any URL on a schedule

We send an HTTP request at your interval and record whether it responded, how fast, and with what status.

Wait for a heartbeat check-in

Your cron job calls a unique URL when it runs. If the check-in does not arrive in time, PulseChecker treats the job as missed.

Watch an AI agent run

Your agent reports in when it starts and when it finishes. We catch the run that hangs and never finishes, the run that errors out, and the run that returns empty or malformed output, and we log every run's duration so you can see the pattern.

New

Your own status page, your own URL

Pick which monitors to show, set a custom address, and let people see what you already know before they have to ask. Free, unlimited monitors shown, yours to turn off any time.

Start free

pulsechecker.dev/s/acme

APIOperational

Nightly export jobOperational

Webhook relayDown

New

Know the moment it breaks — and the moment it's a pattern

Email and a webhook to Slack or Discord on every up/down transition, free on every plan. Set a 30-day uptime target and we alert on the trend too, not just the single check that happened to fail. Paid plans add a text message straight to your phone.

Start free

#incidents

DOWN: API server is down: connection refused

SLA breached30-day uptime: 98.20% / target 99.9%

Text message

PulseChecker: API server is down: connection refused

New

A text can sit unread. A phone call can't.

On Growth and Scale, a critical monitor going down calls your on-call chain in order — an actual phone call, not another notification to swipe away. Nobody presses 1 to acknowledge? We call the next person. No answer from anyone, we keep going until someone does.

Start free

Database is down — escalation chain

Jordan — mobileNo answer
Priya — mobileCalling now...
Sam — mobileAcknowledged — press 1

Escalation stopped — Sam acknowledged after Jordan didn't pick up.

New

Pinging a URL is a commodity. Test the whole flow.

Script a real user journey — log in, add to cart, check out — and we run it in an actual headless browser on a schedule. A single ping only proves the server answered; this proves the thing your users actually do still works.

Start free

Checkout flow

1.Navigate to /login
2.Fill #email, #password
3.Click #submit
4.Assert "Welcome back"

Failed at step 4 — alert sent the moment the run finished.

See status at a glance

Every monitor gets its own history: uptime, response time, and a timeline of incidents, so you know exactly when something broke and for how long.

PulseChecker dashboard showing three monitors, their status, and response times

Start free. Upgrade when you outgrow it.

No credit card to start. Every plan includes email alerts, webhook alerts, SLA breach tracking, and a public status page. Upgrade anytime from your dashboard.