Cronitorex watches your cron jobs, deploy scripts, HTTP endpoints and SSL certificates. Send a ping from any script - get an alert in 60 seconds. No need to build your own monitoring infrastructure from scratch.
# Cron, deploy, ETL, backup, worker - wrap anything in 3 lines curl -sf https://api.cronitorex.com/ping \ -H "Authorization: Bearer $CRONITOREX_API_KEY" \ -d '{"event_type":"ping","monitor":"db-backup","status":"run"}' /usr/local/bin/backup.sh # your script - whatever you run curl -sf https://api.cronitorex.com/ping \ -H "Authorization: Bearer $CRONITOREX_API_KEY" \ -d '{"event_type":"ping","monitor":"db-backup","status":"complete","duration":47.3}'
Works with any script run from shell - bash, Python, GitHub Actions, k8s CronJob, Airflow task, deploy hook.
Most outages do not announce themselves. They look like this:
A pg_dump cron has been exiting with code 1 since the 4th. Nobody noticed, because a failing job writes nothing to a dashboard and sends no email. You find out during a restore, which is the most expensive possible moment.
Renewal was automated, until someone moved the DNS. The certificate ran out at 02:13 and checkout showed a security warning until Monday. Nothing in the stack considered this an error.
The server says the process is up. Users still get a 502 from the load balancer. From the inside everything looks healthy, which is exactly why the request has to come from outside.
Cronitorex was built for these three moments.
Built for developers who want full control over their monitoring stack.
Three pings. Complete visibility.
One HTTP request per ping. Cronitorex correlates them into a timeline, detects missed runs, and pushes alerts within seconds. No agents. No daemons. Just three pings.
Send a run ping at the beginning of your job.
{"status": "run"}Your actual task executes. Cronitorex waits.
/usr/bin/backup.shSend complete or fail. Dashboard updates instantly.
{"status": "complete"}A quick look at what Cronitorex shows you every day. Click through the tabs.
Run finished with exit 1. Alert sent to Telegram and email.
Upstream API returned 401 after a key rotation. Fix in progress.
HTTP check failed 3 times in a row with 503.
Provider incident closed. Checks green again.
Email, webhook, Telegram and Discord on every plan. Slack from Pro. PagerDuty on Business.
External polling and log scraping each miss a whole class of failures. Pings close the gap.
A check tells you the server answered. It cannot tell you the 02:00 backup never started, because there is no URL to ask about a job that did not run.
Logs record everything and alert on nothing. Grepping yesterday's stack trace is archaeology; by the time someone reads it, the damage is done.
A job that reported run and never reported complete is hanging. A job that reported nothing is dead. Both raise an alert within a minute, with exit code and stderr attached.
Cronitorex does both: pings from the inside, checks from the outside. See how it works →
Pick the monitors you want to show and Cronitorex publishes a status page with live state, uptime percentages and incident history. You write updates while you investigate, so support stops answering the same email over and over. Available on every plan, under its own address.
Six typical scenarios where Cronitorex earns its keep.
If it can send an HTTP request, it can be monitored. No agent, no SDK, no firewall rules: pings go out from your side.
One line with curl is enough. The docs have ready snippets for each environment. Browse the docs →
Yes. Cronitorex monitors production cron jobs, HTTP endpoints and SSL certificates every day. Production traffic welcome on every plan, including Free.
Cronitorex exposes a standard HTTP API with run/complete/fail pattern. If your current tool uses a similar ping model, migration is just changing URL and API key in existing scripts. Full API reference at docs.cronitorex.com, and a step-by-step migration guide covers switching from Cronitor, PostPing, and other tools.
Email, Telegram, Discord and webhook notifications are available on all plans. Slack is included from the Pro plan. Webhooks let you connect any HTTP endpoint, enabling integration with any external service yourself.
Yes. Pick which monitors to publish and Cronitorex generates a public status page with live status, uptime percentages and incident history - available on every plan, including Free.
Hosted on our own infrastructure in the EU, GDPR-compliant. All traffic over HTTPS (TLS 1.3) - no ping ever travels in plaintext. The database sits on a private network, accessible only from our application services. User passwords stored as cryptographic hashes. You can rotate your API key at any time from the profile page - the old one stops working immediately. Daily database backups, encrypted, 30-day retention. Full data export and account deletion from the dashboard. We do not sell or share data with third parties. Need an audit report or on-prem deployment? Email hello@cronitorex.com.
Sign up, get an API key, paste the curl into your cron. That's it.