Skip to content

Help keep node-cron dependable.

node-cron has scheduled jobs in Node.js since 2016. Today it runs in 220,000+ repositories at around 20 million downloads a month, with zero runtime dependencies. It is maintained in the open, for free.

If it is part of your stack, sponsoring is a simple way to help keep it that way. Your support goes to the DST and timezone test suite that keeps jobs firing correctly through clock changes, the lifecycle observability that makes production debugging easier, and the ongoing work of holding the dependency count at zero.

npm downloadsused byGitHub starsdependencies

2016
in production since
(~10 years)
20M+
downloads / month
(npm)
220k+
repositories use it
(GitHub “Used by”)
0
runtime
dependencies

Our sponsors

Silver easySAAS

What your sponsorship funds

Correct scheduling through DST and timezones.

A 0 3 * * * job fires once at 3am local, every day, including the two days a year the clock jumps. node-cron never fires twice for the same instant, never fires into a spring-forward gap, and handles 30-minute DST zones, not just the US case. Keeping those guarantees verified against changing timezone data is constant work.

One run across your whole fleet.

Scale to four pods and a naive cron runs your nightly backup four times. distributed: true fires the job on exactly one instance per scheduled time, with a zero-dependency default or a Redis coordinator for high availability, and it fails loudly on deploy rather than silently at 3am.

You find out when a job breaks.

Ten lifecycle events (started, finished, failed, missed, overlap, skipped) mean you are never guessing whether last night's job ran. Runs missed to blocking I/O or a busy event loop are detected and surfaced, not swallowed.

Heavy jobs that don't freeze your app.

Move a CPU-bound or long-running job into an isolated forked process with a single line, and it never blocks your main event loop, while keeping the same lifecycle and events across the process boundary.

Tiers

TierMonthlyWhat you get
Gold$50Large logo at the top of the README, docs, and this page. Visible to developers across 220,000+ dependent repositories. The most visible way to support the project.
Silver$25Logo in the README and on this page, seen by developers in the 220,000+ repositories that already depend on node-cron.
Bronze$10Your logo and link on this page. A meaningful presence that helps keep the library tested and at zero dependencies.
Backer$5Your name and link in the backers list. Every bit adds up to the hours that keep the library tested and at zero dependencies.

Does node-cron help your team? Sponsoring helps keep it maintained, tested, and dependency-free for the years ahead. Every tier makes a difference.

Companies and individuals are equally welcome, from $5 a month.

GitHub Sponsors →Open Collective →

Sponsor through GitHub Sponsors or Open Collective. This page updates automatically from both.

Released in 2016 under the ISC License.