BullMQ & Redis tools

Durabull vs Bull Board

Bull Board is an MIT dashboard for Bull and BullMQ. Embed it in a server with Queue adapters, or use its standalone CLI to discover queues from Redis. Durabull adds a shared workspace for connections, teams, alerting, and MCP; both can inspect and retry existing jobs.

Bull Board website ↗5 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 Bull Board

Choose Bull Board when you already have a Node server, you are fine registering queues in that process, and you want a free in-process UI with no extra service. The CLI is also a reasonable one-shot look at a single Redis.

The case for Durabull

Choose Durabull when queues live across staging and production Redis instances, you do not want to change application code just to get a UI, you need alerts, or you want Claude, ChatGPT, or Codex to inspect and retry jobs through MCP.

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 Bull Board feature comparison
Feature	Durabull	Bull Board
See queues	Redis SCAN for `<prefix>:*:meta`. No app SDK for inspection.	Embed: register adapters. CLI: SCAN one Redis.
App code change	Not for inspection	Required for the embed path
Environments	Many Redis connections per org, grouped by environment	CLI: one deployment. Embed: configured Queue connections
Alerts	Email, signed webhooks, Linear	Custom worker / QueueEvents integration
MCP	Hosted MCP with OAuth, 30 tools, redaction, opt-in writes	No MCP server; JSON HTTP API (OpenAPI)
Job ops	Inspect payloads, logs, stack traces; retry, promote, pause from the dashboard	Retry, promote, remove, clean, pause/resume, edit job data, add jobs, run schedulers
Price	Hosted app is free to start. Self-host under Apache-2.0.	Free (MIT)

Setup

How Bull Board connects

The documented embed path installs @bull-board/api plus a server adapter, then createBullBoard({ queues: [new BullMQAdapter(emailQueue)] }). The CLI and Docker path skip that: npx @bull-board/cli -r redis://localhost:6379 scans Redis for <prefix>:<queue>:meta / <prefix>:<queue>:id keys and rescans every 10 seconds. CLI takes one Redis URL.

Application changes. Embed: yes. Every queue you want to see must be constructed and passed to the board. NestJS forFeature also registers each queue by name or instance. CLI/Docker: no app change, one Redis, optional basic auth.

Queue discovery: CLI/Docker: yes, SCAN under configured prefixes (default bull). --queues turns discovery off. Embed: no discovery. PostgreSQL-backed BullMQ v6 queues are not discoverable via CLI.
Environments: The CLI targets one Redis deployment, with multiple prefixes supported. Embedded Queue instances can use different connections, and separate dashboards can share one server. You implement connection configuration and access control in your application.
Alerts: No built-in notification delivery. Official recipes show how to add alerts with BullMQ worker events or QueueEvents. Optional historical metrics are separate from alerting.
AI & MCP: No official MCP server. The board exposes a JSON HTTP API with an OpenAPI description, and the docs include an AI-agent setup guide for scripting against it.

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.

Bull Board pricing: MIT, free. No paid tier on GitHub, npm, or the docs site.
Bull Board 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 Bull Board and Durabull

Is Durabull a Bull Board alternative?

Yes. Both inspect and manage existing BullMQ jobs. Bull Board offers an MIT embed and standalone discovery CLI; Durabull offers a shared workspace with connection management, alert delivery, and hosted MCP. Choose based on hosting and team requirements.

Does Bull Board auto-discover queues?

The CLI and Docker image do: they scan Redis for Bull and BullMQ meta keys. The embed path does not. You pass each Queue adapter in application code.

Does Bull Board have an MCP server?

No. Bull Board does not ship an MCP server. It exposes a JSON HTTP API (with an OpenAPI description) and documents how to point AI agents at it; Durabull provides a hosted MCP endpoint with OAuth scopes.

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 Bull Board 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