Updated
Ship and run

Background Jobs & Cron

Run work outside the request — sending batches, processing uploads, calling slow AI APIs, nightly cleanups — with retries when it fails.

For your framework or language:ReactNext.js
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Trends

pg-boss gained the most ground in package downloads: 3.9× against the median npm package over a year.

Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.

ToolDownloadsStarsProduct Hunt
Celery10.1M/wk★ 29k—
BullMQ8.2M/wk+46% vs npm★ 9.5k16 followers
Upstash4.7M/wk+92% vs npm—518 followers
Temporal3.7M/wk+59% vs npm★ 23.7k626 followers
RabbitMQ2.9M/wk−51% vs npm★ 13.9k19 followers
Inngest2M/wk+135% vs npm★ 5.9k40 followers
Dagster1.9M/wk★ 16.3k—
pg-boss1.8M/wk3.9× vs npm★ 4.1k—
Prefect1.6M/wk★ 24k2 followers
Trigger.dev935.5k/wk3.4× vs npm★ 16.5k699 followers

The real choice

Hosted job platform or a queue you run. Hosted platforms work on serverless hosting and give you retries, schedules and a dashboard, at the cost of a vendor in your critical path; a queue library is free and fully yours, but needs a long-running worker process and Redis or Postgres to hold the jobs. A durable workflow engine sits between: you run the workers, it keeps each workflow's state so long processes resume after failures. A data pipeline orchestrator answers a different need: it runs scheduled data, ETL and ML pipelines as graphs of dependent steps with a run history, rather than jobs your app enqueues when a user does something.

What makers chose65 live products, each with a source. Not market share.

Pick by situation

Tap the ones that are you — the tools that fit light up below.
  • You deploy to serverless hosting and have tasks that run for minutesTrigger.dev
  • One user action kicks off several steps with waits between themInngest
  • A process runs for days or months and must pick up where it left off after a crashTemporal
  • You only need a scheduled call or a delayed HTTP request on serverlessUpstash
  • You already run a Node server and want a free queue next to it, on Redis or PostgresBullMQ

Compare the tools

Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.

ToolBest for
Hosted job platform2
Trigger.devservice · open source · free tierLong-running TypeScript tasks — AI calls, media processing — that would time out in a serverless function.23+6 open source$0Free935.5k/wk3.4× vs npm

Use it whenA task like video processing or a long AI call keeps hitting your serverless function's timeout.

Trade-offYour job code is deployed to and runs on Trigger.dev's infrastructure unless you self-host it.

llms.txt

Used by Contrive, CopyCopter, devlogs.gg, giselle, Human Behavior and 18 more · in 6 open-source projects.

CopyCopter uses Trigger.dev as a background job manager, making the code cleaner, more scalable and more fun to play with! Trigger.dev is a must-have for NextJS Serverless App.s
CopyCopter, the makerSep 2026 ↗
Inngestservice · open source · free tierEvent-driven, multi-step workflows where each step retries on its own and your code stays in your existing app.16+11 open source$99Pro2M/wk+135% vs npm

Use it whenOne user action fans out into several steps with waits and sleeps in between.

Trade-offPricing scales with executions and steps, so chatty workflows cost more.

llms.txtCLIIn Lovable

Used by Cloudglue, FirstQuadrant, Move AI, North, Productlane and 11 more · in 11 open-source projects.

We also hosted our own Redis-based queue before managing events infra became a job in itself. Inngest has top tier local dev DX and helps our background jobs scale infinitely.
FirstQuadrant, the makerSep 2026 ↗
Durable workflow engine1
Temporalplatform · open source · free tierLong-running, multi-step workflows — payments, onboarding, AI agent loops — whose state must survive crashes and deploys, in Go, Java, Python, TypeScript and more.35+20 open source$5.50Developer (pay as you go)3.7M/wk+59% vs npm

Use it whenA process spans minutes to months and a failed step must resume where it left off, not restart.

Trade-offYou run worker processes, plus the Temporal server or Temporal Cloud billed per action; workflow code must be deterministic.

llms.txt

Used by Breyta.ai, Central, Finyuus, Flexprice, Hoplite and 30 more · in 20 open-source projects.

It powers our multi-step workflows across agent actions. Temporal gives us durability, visibility, and precise control. Battle-tested orchestration with strong developer UX.
RunLLM, the makerSep 2026 ↗
Serverless queue1
Upstashplatform · free tierSimple scheduled calls and delayed HTTP jobs on serverless or edge hosting, via QStash.2$1.00Pay as you go4.7M/wk+92% vs npm

Use it whenYou need a cron trigger or a delayed call on serverless hosting and nothing more.

Trade-offA message is an HTTP call to your endpoint, so the endpoint's time limit still applies to the work.

llms.txtIn v0

Used by inbox-zero, Dub.

We use Upstash for caching and queues – it's been incredibly reliable for us since day one!
Dub, the makerSep 2026 ↗
Self-run queue1
BullMQlibrary · open source · free tierNode apps on a long-running server that already have Redis — free and fully in your control.1+65 open source—8.2M/wk+46% vs npm

Use it whenYou have a server and Redis already running and don't want a new vendor.

Trade-offYou run the worker processes and Redis yourself, and there is no hosted dashboard by default.

llms.txt

Used by Postiz · in 65 open-source projects.

This is the bread and butter of Postiz, this is how we schedule all the posts.
Postiz, the makerSep 2026 ↗

Cost: the cheapest plan that fits job runs or steps 100k runs, job compute time 20 hours, from list prices. Try your own numbers →

Cost as you grow

Each contender's cheapest usable plan as usage rises.

$0$20$100$200$50010501005001k5k10k
UpstashTemporalInngestTrigger.devx: job runs or steps per month (thousand runs), other usage scaled with it · cheapest usable plan at each point, list prices · try your own numbers

Who switches to what

Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes, by developers in general rather than makers only. Pick a flow to see its pull requests.

What Hacker News says

Hacker News commenters choose RabbitMQ most often for background jobs & cron, and like Temporal best (net praise +9%). Among products launched since 2024 that show their choice, 42% use Temporal.

ToolHN comments choosing itNet praise on HNMakers' launches since 2024
RabbitMQ126+3%2% 1
Celery69−17%0% 0
Temporal67+9%42% 21
Dagster27+5%0% 0
Inngest19+23%20% 10
BullMQ17+12%0% 0
Prefect15+13%0% 0
Trigger.dev10+35%38% 19

Comments January 2023 to August 2026 that name the tool in a sentence like "I use" or "we moved to", estimated from a sample Claude read; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. Makers: of 50 launches that show what they use here. HN commenters and makers are different crowds — where they agree and where they split.

Before you choose

How to approach it

Anything that takes more than a few seconds or calls a flaky third-party API belongs in a job, not in the request handler. Make every job safe to run twice, because retries will run it twice. If you deploy to serverless functions, pick a hosted option; if you already run a server and Redis, a library queue is enough.

Common mistakes
  • Firing off a promise without awaiting it in a serverless function; the function is frozen after the response and the work silently never finishes.
  • Putting whole objects in the job payload instead of IDs, so the job acts on stale data by the time it runs.
  • Running scheduled jobs with no alert on failure, so a nightly cleanup can be broken for weeks before anyone notices.

Other options

Real choices most makers here won't need to weigh.

Decided alongside

What the 65 makers' products here chose for their other decisions.