Launching today
Cronhq
Cron jobs that actually run
41 followers
Cron jobs that actually run
41 followers
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.
Products used by Cronhq
Explore the tech stack and tools that power Cronhq. See what products Cronhq uses for development, design, marketing, analytics, and more.
Rust AdventureLearn to build reliable and efficient software in rust
5.0 (4 reviews)
Cronhq only works if Rust is correct, not just fast, the whole product is a promise that a job fires exactly once, and that promise lives in ownership, lifetimes and error handling I couldn't hand-wave. Rust Adventure got me from reading syntax to shipping something real. It's workshop-shaped: you build working things and hit the borrow checker in situations that actually occur, rather than touring language features. The alternatives I tried were either reference material that assumed I already thought in Rust, or tutorials that stopped right before anything concurrent , which is precisely where my problem starts. Cronhq's scheduler and worker are async Rust coordinating through Postgres under load, and that's the part I'd have gotten wrong on my own.