Cronhq launches exactly-once cron scheduling

Cronhq targets a mundane but expensive reliability gap: scheduled jobs that fail invisibly or run twice. Its strongest appeal is giving small teams production-grade scheduling without adding Redis, Kafka, or a proprietary platform dependency.

• –Postgres locks coordinate workers while keeping the architecture simple.
• –Heartbeat monitors cover existing cron jobs Cronhq does not execute.
• –Cron-as-code and live execution tails make schedules easier to review and debug.
• –Exactly-once scheduling still requires downstream idempotency for safe retries and failover.
• –Self-hosting and a five-job free tier make it a credible alternative to hosted cron monitors.