As of today Postqron is available: our developer-first SaaS for managing, syncing and monitoring cron jobs. Define your scheduled jobs in the UI or in a cron.yaml file in your own GitHub repository, and Postqron runs them reliably, retries with exponential backoff on failure, logs every run and alerts you when a job keeps failing.
1. Why we built it
A crontab on a machine is the easiest thing in the world to write and the easiest to forget. It lives on a server nobody watches, it leaves no readable history of what actually succeeded, and when a job stops working you find out downstream — from a missing report, an invoice that never went out, a backup that wasn't there. Postqron exists to move those jobs from "things running somewhere" to things you can observe.
2. Reliable scheduling, without your own cron server
Jobs run on Postqron's infrastructure. Every job carries an explicit timezone, so scheduling stays predictable across daylight-saving changes, and on failure — timeouts, network errors, error HTTP responses — the attempt is retried with exponential backoff, up to a maximum you set per job. There's no machine of yours to keep alive just to fire schedules.
3. Your jobs live in your repository
This is the part we cared about most: with GitHub sync, job configuration lives in a cron.yaml file in your repository. The same jobs go through review, have a diff, have a history — like the rest of your code. Someone joining the project sees what's scheduled by reading the repo, not by asking whoever was there before. If you prefer the UI, use the UI: both routes lead to the same place.
4. A log for every run, alerts on failures
Every attempt records its start and end time, duration, outcome, HTTP status and a truncated excerpt of the response. When a job starts failing persistently, an alert goes out: the point is that a broken job is known right away, not when someone notices the downstream effect.
5. Built for developers
Postqron is API-first: a REST API to create and update jobs, inspect runs and trigger manually, authentication with API keys, and configuration as code. The goal is to let scheduling fit into your scripts and your pipelines, rather than locking you into a dashboard.
Postqron is available now at postqron.com. If you want to work out how to move the jobs you already run in production, let's talk: the first consultation is free.