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

Bee-Queue review

Free#30 of 36 in Task Queue Software

A focused, self-hosted queue for lightweight JavaScript workers and short jobs.

6.3/10Editor score
Bee-Queue6.3 Visit Bee-Queue

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Bee-Queue is an open-source JavaScript library for building distributed worker pools with Redis. It is aimed at developers who need applications to enqueue short, real-time jobs and process them across multiple processes or servers. Its Node.js focus, callback- and Promise-compatible API, and self-hosted deployment model make it a practical fit for teams that want to manage queue infrastructure directly rather than consume a hosted service.

The feature set covers the core controls expected in a task queue. Workers can process jobs concurrently, while configurable retries support immediate, fixed, and exponential backoff. Bee-Queue also handles delayed and scheduled jobs, job timeouts, stalled-job reprocessing, progress reporting, and Pub/Sub events. These capabilities give developers control over common failure and timing scenarios without narrowing the API to a single processing pattern. Redis is the primary integration, and Arena is also listed in the ecosystem, keeping the platform fit focused rather than broad.

Bee-Queue is open source and self-hosted, so its cost model centers on developer-managed operation instead of hosted plan tiers. That approach suits teams already comfortable running Redis and JavaScript workers, but it places setup, capacity, monitoring, and maintenance responsibilities with the implementation team. The project guidance favors keeping job data small, and the queue does not provide a dedicated dead-letter queue. Choose Bee-Queue for lightweight Node.js jobs where Redis-backed distributed workers and configurable retries are the priority. Teams seeking a hosted queue, broader integration coverage, or a built-in dead-letter workflow should consider another option.

Bee-Queue pros and cons

  • Where it wins
    • Distributed workers can run across processes and servers.
    • Supports retries, backoff, delays, scheduling, and timeouts.
    • Offers progress reporting, Pub/Sub events, and flexible APIs.
  • Where it doesn't
    • Requires developers to operate the queue and Redis infrastructure.
    • Designed for small job data rather than large payloads.
    • Does not provide a dedicated dead-letter queue.

Bee-Queue 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