CronWatch

About CronWatch

CronWatch records every run of your scheduled jobs in your own database, and alerts you when one is missed, fails, gets stuck, runs slow, or costs too much. It is a library, not a service, requiring no server to run or account to create. With CronWatch, you can monitor jobs in various programming languages including TypeScript, Ruby, Python, PHP, Go, Rust, Elixir, Java, and .NET.

What CronWatch is used for

• SaaS teams catching nightly backups and billing jobs that silently stop running
• Developers alerting on scheduled LLM and API jobs that run up unexpected costs
• Data teams flagging stuck or slow ETL loads before morning dashboards go stale
• Regulated teams keeping job run history in their own database, not a vendor's
• Agencies monitoring cron jobs across client stacks in nine languages

CronWatch pricing

Free and open source.

CronWatch alternatives

Tools the builder names as the closest alternatives.

• https://healthchecks.io
• https://cronitor.io
• https://deadmanssnitch.com
• https://sentry.io/for/cron-monitoring/
• https://betterstack.com

CronWatch FAQ

Is CronWatch a hosted service?

No. CronWatch is a library you add to your app. There is no server to run and no account to create.

Where is my job data stored?

In your own database. Every run of your scheduled jobs is recorded there, so the data never leaves your infrastructure.

What does CronWatch alert on?

It alerts you when a job is missed, fails, gets stuck, runs slower than expected, or costs more than expected.

Which languages are supported?

TypeScript, Ruby, Python, PHP, Go, Rust, Elixir, Java, and .NET.

How is it different from Healthchecks.io or Cronitor?

Those are hosted services that your jobs ping. CronWatch runs inside your app and keeps run history in your own database, and it also catches slow and costly runs.