BullMQ & Redis tools

Durabull vs Workbench

Q: Does Workbench require registering queues in application code?

Sometimes. The embed quick start passes `queues: [Queue]`. Passing `redis` enables auto-discovery. Docker wants `QUEUE_NAMES`. The macOS app uses a Redis URL.

Workbench is an MIT BullMQ dashboard with embedded, standalone, and macOS options. It offers Redis discovery, Slack/Discord/webhook alerts, and a local MCP proxy. The main decision is whether you prefer a dashboard you deploy or a hosted workspace shared across a team.

Workbench website ↗4 primary references

System map

Your applicationProducers & workers

enqueue / process

Redis + BullMQQueue state & job lifecycle

runtime

inspect / operate

DurabullDashboard · alerts · MCP

operations

A dashboard observes and operates your existing queues.

The case for Workbench

Choose Workbench for an MIT dashboard you can embed or open on a Mac, with Slack/Discord/webhook alerts and local MCP. Raise maxQueues when discovery needs to include more than its default 100 queues.

The case for Durabull

Choose Durabull when you operate many connections, you do not want to mount a dashboard in the app, or you want Claude, ChatGPT, or Codex to use a hosted MCP URL with OAuth scopes rather than a local proxy.

Capabilities

The details that change the decision

Compare the documented deployment modes. “Not documented” means we did not find a vendor claim, not proof that a capability is impossible. Check the primary sources.

Durabull versus Workbench feature comparison
Feature	Durabull	Workbench
See queues	Redis SCAN for `<prefix>:*:meta`. No app SDK for inspection.	queues[] or redis (maxQueues default 100). Docker: QUEUE_NAMES.
App code	Not for inspection	Embed mounts in the app; desktop does not
Environments	Many Redis connections per org, grouped by environment	One Redis per process in published docs
Alerts	Email, signed webhooks, Linear	Slack, Discord, webhook
MCP	Hosted MCP with OAuth, 30 tools, redaction, opt-in writes	Local stdio proxy to one dashboard
Price	Hosted app is free to start. Self-host under Apache-2.0.	Free (MIT)

Setup

How Workbench connects

Embed default: workbench({ queues: [emailQueue] }). Auto-discovery: pass redis instead; queues is required unless redis is set. maxQueues defaults to 100. Docker uses QUEUE_NAMES (default default), not SCAN. The macOS app takes a Redis URL and auto-discovers. Bull (legacy) is not supported.

Application changes. Embed: you mount Workbench in the app. You either pass Queue instances or a Redis URL. Docker: name the queues. Desktop: no app change.

Queue discovery: Yes when redis is set, or on the macOS app. Configurable default cap of 100. Docker standalone lists names in QUEUE_NAMES.
Environments: Published config is one Redis per Workbench process. Docs do not describe a multi-connection environment workspace.
Alerts: Slack, Discord, generic webhook. Triggers include job_failed, job_stalled, retries_exhausted, failed_backlog, no_workers_with_backlog. Rules live in Redis. Nothing sends until you configure contact points.
AI & MCP: Yes. @getworkbench/mcp is a local stdio proxy to one running dashboard (WORKBENCH_URL). Roughly 20 inspect/operate tools (docs list 18; package 0.5.1 ships 23). Not a hosted multi-tenant MCP URL.

Economics

Understand what you are paying for

Different products, different cost boundaries. Durabull’s hosted app is free to start and covers its dashboard. Redis, worker compute, storage, networking, and operational work remain yours. A runtime’s usage charges may cover orchestration or compute. The prices here are not a total-cost or savings benchmark.

Workbench pricing: MIT, free. Vendor blog: no paid tier, no telemetry, no account required.
Workbench license: MIT.
Durabull: Hosted dashboard is free to start. Redis, worker compute, and infrastructure operations remain your costs. Check the pricing page for current terms. Apache License 2.0 (OSI-approved open source). Self-host on your own infrastructure.

Questions about Workbench and Durabull

Does Workbench require registering queues in application code?

Sometimes. The embed quick start passes queues: [Queue]. Passing redis enables auto-discovery. Docker wants QUEUE_NAMES. The macOS app uses a Redis URL.

How many queues can Workbench auto-discover?

The documented default is maxQueues: 100, and you can raise it in configuration. It is a scan-cost setting, not a paid tier or a fixed product limit.

Evidence

Sources & methodology

Reviewed against vendor documentation, public pricing, and source repositories. This is a documentation comparison, not a hands-on benchmark. Vendor docs may describe different editions or deployment modes; confirm those details before purchasing.

Durabull details: product documentation, pricing, and MCP reference. Found a change? Send a correction.

Continue your research

Practical guides

Explore Workbench alternatives →

Connect Redis. Queues appear.

Inspect your Redis-backed BullMQ queues in one place. Hosted Durabull is free to start.

Start Free Connect your agent