Cron jobs fail in silence. Two servers run the same crontab and your billing job fires twice. A job dies and nobody notices for weeks. Cronhq is a scheduler built around one guarantee: exactly-once execution, enforced by Postgres locks — not best-effort. Around it: retries with backoff, HMAC-signed webhooks, heartbeat monitors for jobs we don't run, and alerts that fire once on failure and once on recovery. Rust on Postgres. MIT-licensed, self-hostable, same image we run. Free tier: 5 jobs.
Cronhq Reviews
The community submitted 1 review to tell us what they like about Cronhq, what Cronhq can do better, and more.
4.0
Based on 1 review
Review Cronhq?
AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Reviews
Most Informative
Thank you for testing CronHQ this thoroughly, this is genuinely valuable feedback.
I’m glad the five-minute schedule, retries and heartbeat setup worked smoothly. The missing recovery alert isn’t expected, so I’m investigating that. If you’re comfortable sharing the approximate test time or job ID through hello@cronhq.xyz, it would help me trace the exact transition.
You’re also right that each retry attempt should be clearer in the execution history, with its own duration, HTTP status and metadata. I’m reviewing that alongside the documentation and the current visibility of the repository and CLI.
Really appreciate the detailed and balanced review.