Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

BullMQ review

Freemium#4 of 36 in Task Queue Software

Deep background processing for production Node.js teams that need queue control.

8.9/10Editor score
BullMQ8.9 Visit BullMQ

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

BullMQ is an open-source background-job and message-queue library for distributed job processing. It is designed for production teams building microservices, worker-based applications, and polyglot systems, with official support for Node.js, Bun, Python, Rust, Elixir, and PHP. The core model uses queues and workers, while the feature set covers delayed jobs, scheduled jobs, retries, rate limiting, priorities, concurrency, job flows, and dependencies.

Pricing separates the free open-source option from commercial licensing. Standard is listed at $139 USD per deployment per month, or $1,395 USD per deployment per year, and adds Groups, Batches, Observables, and Professional Support. Standard is available to organizations with fewer than 100 employees; larger organizations require Enterprise licensing. Enterprise includes all Standard features plus volume discounts, priority support, custom agreements or an MSA, and payment by purchase orders. Embedded adds redistribution rights, product embedding, and the ability to sell to customers.

BullMQ fits teams that want detailed control over queue behavior, including fixed, exponential, and custom retry backoff; FIFO, LIFO, priority, and rate-limited jobs; dead-letter queues; and parent-child flows. It connects with Redis, Valkey, DragonflyDB, AWS ElastiCache, Upstash, and PostgreSQL, and supports self-hosted and API deployments. Polyglot interoperability broadens its fit beyond Node.js applications. Teams should choose BullMQ when queue depth, scaling controls, and datastore flexibility matter. It is less suitable for organizations that do not want to operate a self-hosted queue architecture or that fall outside Standard licensing eligibility.

BullMQ pros and cons

  • Where it wins
    • Retries, scheduling, dead-letter queues, priorities, and dependencies
    • Concurrency control and horizontal worker scaling
    • Open-source library with Node.js and polyglot support
  • Where it doesn't
    • Runs on Redis-compatible backends
    • Standard licensing is limited to organizations under 100 employees
    • Commercial pricing is charged per deployment

BullMQ fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update