Progress-aware monitoring for unattended jobs

See where your job is.

Built for engineers and operators running scheduled or long-running unattended jobs. Unlike a simple heartbeat check, PingStep tracks the named stage your job reached, so lost visibility is always clear without you checking logs or guessing.

Monitor a job

Send a few small lifecycle events. PingStep never collects raw logs or your job's data — they stay wherever they already are.

Built for the moment after a job starts.

Current stage, not just “running”

Your script reports meaningful stages, so you can see the last progress marker it actually reached.

Lost visibility is clear

When updates stop, PingStep marks the run stale. It does not pretend that silence means healthy.

Small, safe updates

Send lifecycle events over HTTPS. PingStep does not need raw logs, payloads, SQL, credentials, or customer data.

How PingStep works

01

Create a job

Give it a simple, non-sensitive name and choose how often it normally reports an update.

02

Send events

Your script sends a start event, useful stages as it works, and a clear success or failure at the end.

03

See the last reported stage

Open PingStep to see the last reported stage. If updates stop, it becomes stale.

Simple plans. No surprise usage bill.

Start free, then pay only for the capacity you use.

Free

US$0

1 job · 100 runs / 30 days

Use PingStep on a real job and see if it helps.

Start free

Scale

US$49 / month

50 jobs · 50,000 runs / 30 days

For higher-volume recurring jobs.

Choose Scale

View full pricing →

Status means one clear thing.

PingStep reports what it has received. It does not guess whether a silent job is healthy.

Running

Recent updates are arriving. The last reported stage is shown.

Stale

Updates stopped past the time you set. The job may still be running, but PingStep cannot confirm it.

Late

The run has been active longer than expected. Late can happen alongside Running or Stale — it is a separate signal, not a replacement for either.

Succeeded

Your script explicitly sent a successful completion event.

Failed

Your script explicitly sent a failed completion event. It is never shown as complete.

Only the signal you choose.

PingStep stores your account email, job names, lifecycle events, timestamps, and token hashes so it can show a run’s status.

Never your job’s contents.

It does not collect raw logs, command output, SQL, credentials, or the files your job processes. Read the privacy details.

Stop guessing whether a job is still moving.

Open PingStep