bree

Bree handles that with worker threads so your main process doesn't block. Basically, it's cron for your Node.js app, but each job runs in its own thread and can't crash your server.

MIT license, JavaScript. Each job runs in a Node.js worker thread with its own memory space. If a job crashes, your app keeps running. Supports cron expressions, intervals, one-time runs, and human-readable schedules ("every 5 minutes"). Built-in concurrency control. Prevent the same job from running twice.

Fully free. It's a library. No paid tier, no hosted version. Setup is simple: install the package, define your jobs as separate files, configure the schedule. The worker thread approach means jobs are truly isolated. A memory leak in one job doesn't affect your app.

Solo projects and small apps: Bree is a clean solution when you need background jobs without adding Redis or a separate queue system. The catch: Bree runs in-process, which means if your server restarts, scheduled jobs reset. There's no persistence layer. Missed jobs don't retry automatically. For durable job processing that survives restarts, you need BullMQ (backed by Redis) or Temporal. Bree is best for periodic tasks where missing one run isn't catastrophic.