1
Solo founder
Your production cron crashed Saturday. Find out Sunday morning when customers wake up and complain? Cronitorex pings you in 60 seconds - email, Slack, webhook to any endpoint.
Sleep through the night.
Backups that stop, pipelines that stall, certificates that expire. Three deep dives into the jobs teams lose the most money on when nobody is watching.
Six typical scenarios where Cronitorex earns its keep.
Your production cron crashed Saturday. Find out Sunday morning when customers wake up and complain? Cronitorex pings you in 60 seconds - email, Slack, webhook to any endpoint.
Hundreds of crons spread across 12 servers. Cronitorex shows them all in one view, alerts on missed runs, captures stderr on fail, dashboard tells you what crashed today without ssh-ing into 6 machines.
Each client = separate tag, own notifications, own dashboard. Onboard a new client in 5 minutes - monitoring their crons comes free. No logging into 30 different panels.
Hundreds of batch jobs, nightly ETL processes, data pipelines. Cronitorex hooks into any task - ping run at the start, complete on success, fail on any exception. Spot a broken pipeline before downstream tables go stale.
Hourly catalog imports, payment webhooks, stock sync to 3 warehouses, EOD reconciliation. When any of them silently stops, you lose orders. Cronitorex pages you the moment one misses its window.
90-day event history, audit trail, SSL expiry, SLA reporting. CSV export, archives, no log stack to maintain. Show auditors your backup ran every day for the past year.
A backup script that fails quietly is worse than no backup, because you stop worrying. Wrap the nightly pg_dump in two pings and Cronitorex confirms every single run.
If the ping never arrives, you get a missed alert in the morning, not a surprise during a restore.
#!/usr/bin/env bash
ping() {
curl -fsS "https://api.cronitorex.com/ping/nightly-backup?status=$1" \
-H "Authorization: Bearer $CRONITOREX_API_KEY" >/dev/null
}
ping run
pg_dump -Fc app_db > /backups/app_$(date +%F).dump \
&& ping complete || ping fail Pipelines rarely die loudly. They slow down, overlap and quietly skip windows. Send the duration with the complete ping and Cronitorex tracks how long every run takes.
A series id ties the run and complete pings of one execution together, so overlapping runs never get mixed up.
t0 = time.time()
requests.get(API, params={"status": "run", "series": run_id})
rows = extract_and_load()
requests.get(API, params={
"status": "complete",
"series": run_id,
"duration": round(time.time() - t0, 1),
}) Agencies renew dozens of certificates on different dates, issued by different providers. One expired domain is one very unhappy client.
Add each domain as an SSL monitor with 30 and 7 day thresholds and tag it per client. The dashboard shows the next expiry across the whole portfolio.
client-acme.com valid 62 days client-globex.com valid 118 days client-initech.com warn 6 days client-umbrella.com valid 41 days thresholds: 30 days · 7 days
Sign up, get an API key, paste the curl into your cron. That's it.