Cronhub Alternative: Where to Go After the Shutdown
Cronhub shut down on 30 June 2026. If you are still looking for a replacement, read the scheduling caveat first.
Cronhub shut down on 30 June 2026, and paid subscriptions were cancelled on 31 May 2026. If you are reading this looking for a replacement, the first thing to establish is whether you used Cronhub to run your jobs or only to watch them, because those need different tools.
Shutdown dates below come from the notice Cronhub published on cronhub.io before closing. Data was deleted at shutdown, so there is nothing left to export.
What Cronhub actually did
Cronhub was two products in one account. It was a scheduler that fired HTTP requests at your endpoints on a cron expression, and it was a monitor that watched for heartbeat pings from jobs running on your own infrastructure.
It launched in 2018, was built by a single developer, and had a loyal following including Buffer and ProtonMail. Losing it was a genuine loss to this category.
Most replacement guides gloss over the split. If Cronhub was firing your jobs, a monitoring tool will not replace it, and you will discover this when the jobs stop running.
The honest caveat: SensaCat does not schedule
SensaCat replaces the monitoring half only. It does not run your jobs. If you relied on Cronhub's scheduler, you need either a real scheduler or a crontab on a box you control, and then a monitor on top.
For the monitoring half, the migration is one line. Point your job's existing heartbeat call at a SensaCat ingest URL and set an expected interval with a grace period.
Where SensaCat goes further than Cronhub did is the other three failure types. Cronhub watched jobs. It had no credential expiry, no domain or SSL expiry, and no multi-step process tracking.
What to replace each half with
| What you used Cronhub for | Replace with | Notes |
|---|---|---|
| Running jobs on a schedule | A scheduler, or crontab on your own server | SensaCat does not do this |
| Heartbeat monitoring of your own jobs | SensaCat, Healthchecks.io, Cronitor | One curl call, same pattern as Cronhub |
| Alerts when a job runs long | SensaCat grace periods | Buffer past the expected interval before alerting |
| Alerts when a job fails loudly | SensaCat explicit failure reporting | POST status failure for an immediate alert |
| API key and credential expiry | SensaCat credentials, or TokenTimer | Cronhub never covered this |
| Domain and SSL expiry | SensaCat domains, or Oh Dear | Cronhub never covered this |
| Multi-step process tracking | SensaCat business flows | Cronhub never covered this |
Migrating the monitoring half
Create a monitor, set the expected interval to match the job's schedule, add a grace period generous enough to absorb normal timing jitter, and replace the Cronhub ping URL in your script. Nothing else in the job changes.
If you are picking a replacement now rather than in June, you have the luxury of choosing on fit instead of deadline. Healthchecks.io is the better pick if cron is genuinely all you need and you want an open-source option you can self-host.
SensaCat is the better pick if the Cronhub outage made you notice how many other things nobody is watching. Start free: Starter is $0 forever.