
Cron jobs that actually run
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 is a scheduler designed to ensure exactly-once execution of cron jobs, utilizing Postgres locks to prevent duplicate runs. It offers features like retries, HMAC-signed webhooks, and heartbeat monitors, and is available as an MIT-licensed, self-hostable solution with a free tier for up to five jobs.
Scored deterministically. Only candidates that fire a story trigger are sent to a model, so this one has no written angle.
Describes itself in terms almost no other launch uses: "Cron jobs that actually run"
Gaps in our data, not findings about the product. Their weight is redistributed across the 5 we did measure.
A source that found nothing is a measurement. A source that has not run is a gap. Neither means the launch lacks the thing.