“This is the bread and butter of Postiz, this is how we schedule all the posts.”
Background Jobs & CronMaker says so · source ↗
BullMQ
Node.js library for Redis-backed job queues, handling retries, delays, priorities and rate limiting for background processing.
65 open-source projects declare BullMQ in their code; 1 maker's product we track uses it. What makers like most: It is a mature, well-liked production queue on Redis, adding scheduled and cron jobs in a few lines. Their most common complaint: It requires running Redis as extra infrastructure and another single point of failure next to the main database. On GitHub, 3 public pull requests moved projects to BullMQ from tools we list, and 3 moved them away.
Profile checked
Works with AI agents:llms.txtHow makers use BullMQ
Makers' products we track use BullMQ for background jobs & cron (1).
What BullMQ is used for
BullMQ vs the alternatives makers chose
For background jobs & cron, 1 of the 81 makers' products we know the choice of picked BullMQ (1%), behind Temporal (43%).
| Option | Makers' products | Free for | At 10,000 users | Open source | |
|---|---|---|---|---|---|
| 35 43% | ~1,800 users | $5.50/mo · Developer (pay as you go) | Yes | ||
| 23 28% | ~20,000 users | $0/mo · Free | Yes | ||
| 16 20% | ~5,000 users | $99/mo · Pro | Yes | ||
| 3 4% | — | — | Yes | ||
| 3 4% | — | — | Yes | ||
| 2 2% | ~10,000 users | $1.00/mo · Pay as you go | No | ||
| 1 1% | — | — | Yes |
For background jobs & cron: how many of the 81 makers' products we know the background jobs & cron of chose each option, and what each costs at 10,000 users.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for.
When to use BullMQ, and when not
Pick BullMQ if
- You already run a Node server and want a free queue next to it, on Redis or Postgres. Background Jobs & Cron →
Something else fits better if
- You deploy to serverless hosting and have tasks that run for minutes: Trigger.dev.
- One user action kicks off several steps with waits between them: Inngest.
- A process runs for days or months and must pick up where it left off after a crash: Temporal.
- You only need a scheduled call or a delayed HTTP request on serverless: Upstash.
BullMQ is a job queue library you add to your own application. Your web code puts a job on a queue, and separate worker processes pick it up and run it, so slow tasks like sending email or calling an LLM run outside the request.
More about BullMQ
The whole model is four classes: Queue (add, pause and inspect jobs), Worker (process them), QueueEvents (listen for completions and failures) and FlowProducer (parent and child jobs that depend on each other). Queue state lives in Redis by default, or, in newer versions, in PostgreSQL 13+ through an optional backend with the same API. Workers can run on one machine or many. The main library is for Node.js, with ports for Python, Elixir, PHP, .NET and Rust.
What you get: delayed, prioritized and repeating jobs, retries with backoff, deduplication, global concurrency and rate limits, sandboxed processors for CPU-heavy work, and Prometheus and OpenTelemetry hooks. There is nothing to sign up for; you run Redis (self-managed or a host such as ElastiCache, or a tested alternative such as Dragonfly) and your own workers. BullMQ Pro, a commercial drop-in build, adds features such as job groups, plus support from the authors.
The catch is that you operate the infrastructure. Redis must be set to persist data and never evict keys, workers need sensible reconnect settings, and a worker that blocks the event loop can let jobs "stall" and be retried or failed. There is no hosted dashboard; third-party tools such as Taskforce.sh fill that gap.
How BullMQ itself is built
3 tools, from its own code, website and Product Hunt page.
BullMQ pros and cons
What makers like most: It is a mature, well-liked production queue on Redis, adding scheduled and cron jobs in a few lines. Their most common complaint: It requires running Redis as extra infrastructure and another single point of failure next to the main database.
Pros
- It is a mature, well-liked production queue on Redis, adding scheduled and cron jobs in a few lines. HNHN 2HN 3HN 4
- Teams that hit throughput limits with Postgres-backed queues moved to it and stopped fiddling with tuning. HNHN 2
- Its architecture is simple, with the API pushing to Redis and workers pulling, and it gets high availability through Redis Sentinel or Cluster. HNHN 2
- NestJS decorators make adding it to an existing app nearly effortless. HN
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
What Hacker News says about BullMQ
On Hacker News, 16% of comments about BullMQ recommend it and 4% criticize it: net praise +12%.
By year
| Year | Comments choosing it, per month | Net praise |
|---|---|---|
| 2023 | 0.3 | — |
| 2024 | 0.5 | +11% |
| 2025 | 0.2 | — |
| 2026 (8 mo) | 0.6 | +22% |
In their words
- “switched to Redis+BullMQ and have never looked back ever since.” HN, Jan 2026
- “We are very glad we migrated off of PG for our work queues.” HN, Jan 2026
- “We found bull had a much lower throughput, after a lot of tuning compared even to rabbit out of the box.” HN, Sep 2024
Hacker News comments January 2023 to August 2026 that name BullMQ in a sentence like "I use" or "we moved to", Claude read a sample of 26 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.
Reliability and open issues
The most wanted open issue on GitHub has 39 👍.
Most wanted on GitHub
- [Feature request] search a specific job👍 39 · opened Aug 2023 · active Oct 2026
- Support for valkey glide👍 28 · opened Feb 2025 · active Oct 2025
- Migrate to official node-redis👍 25 · opened Mar 2024 · active Jun 2026
- Stop/Abort a running job👍 19 · opened Jul 2021 · active Jan 2026
Who switches
As many projects move to as away from BullMQ: 3 pull requests in, 3 out; the most come from Trigger.dev and leave for Temporal.
Trigger.dev → BullMQ3 PRs
- feat(web): migrate web jobs from Trigger.dev to BullMQ (@buckt/jobs)joaopcm/buckt · 2026-05-29
- feat(api): migrate background jobs from Trigger.dev to BullMQ + Workbenchjoaopcm/buckt · 2026-05-29
- Migrate from trigger.dev to BullMQisntfunny/kitchenpace · 2026-03-01
BullMQ → Temporal3 PRs
- Migrate job execution from BullMQ to Temporal workflowsblu59204/CareerCraftsAI · 2026-09-26
- feat: migrate from BullMQ to Temporal for workflow orchestrationNOJV-TW/NOJV · 2026-04-02
- Moving from BullMQ to Temporal - big changegitroomhq/postiz-app · 2026-01-05
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.
Who uses it
1 makers' products, each linked to the source that shows it, and 65 open-source projects that declare it in their code.
None of these in makers' own words.
Open source: a project that declares BullMQ as a dependency in its public code — verifiable, but not necessarily a live product.
What its projects tell coding agents
32 of the 43 open-source products built with BullMQ that were worked on in the last 180 days keep instruction files for coding agents — 74%, against 53% of all the projects we read. AGENTS.md is in 23, CLAUDE.md in 19.
Alternatives to BullMQ
All alternatives by situation →Questions makers ask about BullMQ
What is BullMQ used for?
Node.js library for Redis-backed job queues, handling retries, delays, priorities and rate limiting for background processing. Makers' products we track use it for background jobs & cron (1).
What are the pros and cons of BullMQ?
Pros makers name: It is a mature, well-liked production queue on Redis, adding scheduled and cron jobs in a few lines. Teams that hit throughput limits with Postgres-backed queues moved to it and stopped fiddling with tuning. Its architecture is simple, with the API pushing to Redis and workers pulling, and it gets high availability through Redis Sentinel or Cluster. Cons: It requires running Redis as extra infrastructure and another single point of failure next to the main database. It is a queue, not a workflow engine, so teams hand-build durable multi-step workflows on top of it.
What are the alternatives to BullMQ?
For background jobs & cron, the other options makers' products we track chose most are Temporal (35), Trigger.dev (23), Inngest (16), Dagster (3), RabbitMQ (3), Upstash (2). Open source or self-hostable among them: Temporal, Trigger.dev, Inngest, Dagster, RabbitMQ. Each alternative, with the situation it fits, is on the BullMQ alternatives page.
Do developers switch to or away from BullMQ?
On GitHub, 3 public pull requests moved projects to BullMQ from tools we list, most from Trigger.dev (3); 3 moved them away, most to Temporal (3).
When should you use BullMQ?
You already run a Node server and want a free queue next to it, on Redis or Postgres (background jobs & cron). Something else fits better if: you deploy to serverless hosting and have tasks that run for minutes, pick Trigger.dev; one user action kicks off several steps with waits between them, pick Inngest.
Do I need Redis, or can I use Postgres?
Redis is the default and most tested backend, but BullMQ also ships an optional PostgreSQL backend (PostgreSQL 13 or newer) that runs the same Queue and Worker API, for teams that would rather not run Redis or want jobs stored next to their relational data. source ↗
How should Redis be configured for production?
Turn on persistence (BullMQ recommends AOF with roughly one fsync per second) and set maxmemory-policy to noeviction, because BullMQ breaks if Redis evicts keys. Many hosted Redis services do not enable persistence by default. source ↗
Which Redis alternatives and hosts work?
BullMQ needs Redis 6.2.0 or newer compatibility, and not every Redis alternative behaves correctly. The docs list vendors that are tested regularly, including Dragonfly, and hosting notes for AWS ElastiCache and MemoryDB. source ↗
Can I use BullMQ from Python?
Yes. There is a Python package installed with pip that uses asyncio and provides Queue and Worker classes against the same Redis queues. source ↗
What happens if a worker crashes mid-job?
Active jobs must keep renewing a lock. If a worker stops doing so, the job is detected as stalled and moved back to waiting, or failed permanently once it exceeds maxStalledCount (default 1). CPU-heavy code that blocks the event loop can also trigger stalls. source ↗
Can I migrate from Bull to BullMQ in place?
Not safely; the two have diverged too far for backward compatibility. The recommended route is to create new queues for BullMQ, run both sets of workers until the old Bull queues drain, then retire them. source ↗
What does BullMQ Pro add?
It is a commercial drop-in replacement with extra features, such as job groups with their own concurrency and rate limits, plus dedicated support from the authors, licensed per organization with a free trial. source ↗
Is BullMQ free?
Yes — there is a free tier a small product can run on; paid use starts at $139/mo (Pro). source ↗
Is BullMQ open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with BullMQ?
It serves an llms.txt docs index.
Who uses BullMQ?
1 makers' products we track, each with a source, and 65 open-source projects declare it in their code. source ↗