QueueHub vs Arena: The BullMQ Arena Dashboard Compared

Before Bull Board became the default, there was Arena — a self-hosted web UI for Bull and BullMQ queues, originally authored by the mixplex team. For a few years it was the way to get a graphical view of your Redis-backed job queues without writing your own admin panel.

Arena still works. You can clone the repo, run it, and see your queues. But its maintenance cadence has slowed to a trickle, the UI has not kept pace with modern BullMQ features, and the deployment story has not evolved. For new projects evaluating BullMQ dashboards in 2026, Arena is worth understanding — and worth comparing carefully against modern alternatives.

This post compares Arena against QueueHub, a hosted multi-backend dashboard for BullMQ, BeeQueue, and Amazon SQS.

TL;DR Comparison

Dimension	Arena	QueueHub
Deployment	Self-hosted (clone + run)	Hosted SaaS
Backends	Bull, BullMQ	BullMQ, BeeQueue, Amazon SQS
Maintenance status	Minimal / sporadic	Actively developed
UI quality	Functional, dated	Modern, real-time
Queue metrics	Basic counts	Throughput, latency, failure rate, history
Job operations	Retry, remove	Retry, promote, delete, reprioritize, bulk
Auth	None built-in	SSO + RBAC
Multi-user / teams	Single-user	Workspaces, seats, audit log

What Is Arena?

Arena is an open-source Node.js app that exposes a web UI for Bull and BullMQ queues. You configure it with a JSON file listing the Redis connections and queues you want to expose, then run it as a standalone process (or inside a container).

A typical config looks like:

{
  "queues": [
    {
      "name": "email",
      "hostId": "production",
      "redis": {
        "host": "redis.internal",
        "port": 6379
      }
    },
    {
      "name": "image-processing",
      "hostId": "production",
      "redis": {
        "host": "redis.internal",
        "port": 6379
      }
    }
  ]
}

You then start the server:

npm install
npm start
# Arena listens on http://localhost:4567

That's it. You point a browser at it and see your queues.

Where Arena Was Good

• Zero application code changes. Unlike Bull Board, Arena doesn't need to be mounted inside your app — it's a standalone process that connects to Redis on its own.
• Multi-host support. The hostId field let you group queues across multiple Redis instances, useful for multi-service setups.
• Simple mental model. One JSON config, one process, one UI.

Where Arena Has Fallen Behind

• Maintenance. The Arena repository sees infrequent commits. Bug reports sit for months. New BullMQ features (e.g., flows, rate limiters, prioritized jobs) often lack first-class UI.
• No authentication. Arena exposes a completely open web UI. You must layer your own auth (basic auth, OAuth proxy, mTLS) in front.
• No RBAC or audit. Once inside, anyone can do anything to any queue.
• No real-time updates. Pages are request/response; you refresh manually.
• Dated UI. The interface is functional but has not kept up with modern web UX expectations.
• Single backend. Bull/BullMQ only. No BeeQueue or SQS.

What Is QueueHub?

QueueHub is a hosted dashboard for Redis-backed and SQS-backed job queues. Where Arena asks you to clone a repo and run a process, QueueHub asks you to create an account and point it at your Redis.

Key properties:

• Multi-backend. BullMQ, BeeQueue, and SQS in one UI.
• Hosted. No Docker image, no process to supervise, no reverse proxy to configure.
• Team-first. SSO, RBAC, audit log, workspaces.
• Real-time. WebSocket push for queue depth, job transitions, and metrics.

UI Quality and Daily Experience

Arena's UI is utilitarian. You get a queue list with counts, a job list per queue, and a detail view for individual jobs showing data, opts, and stacktrace. It works. It does not delight.

QueueHub's UI was designed in 2025+ for engineers who use a queue dashboard every day:

• Real-time queue cards showing depth, throughput, failure rate, and p95 latency.
• Color-coded job states with inline error preview.
• Expandable JSON for data, opts, and returnvalue with syntax highlighting and base64 detection.
• Filterable job lists — filter by state, by job.name, by data field, by error pattern.
• Bulk selection with safe confirmations.

For an on-call engineer at 3am, the difference between "refresh until the queue drains" and "watch the queue drain in real time" is significant.

Queue Metrics

Arena

Arena shows basic counts per queue: waiting, active, completed, failed, delayed. It does not compute throughput, latency percentiles, or historical trends. If you want "jobs per second over the last hour," you need a separate monitoring tool.

QueueHub

QueueHub computes and visualizes:

• Throughput (jobs/sec, jobs/min, jobs/hour).
• Latency p50, p95, p99 (where supported by the backend).
• Failure rate with per-error grouping.
• Queue depth history over configurable windows.
• Worker metrics (where exposed).

These metrics are first-class — you don't need to wire up Grafana to answer "is this queue healthy?"

Job Operations

Arena

Arena supports the core job operations: retry a failed job, remove a completed job, view job data. It does not support bulk operations beyond basic "clear all completed" / "clear all failed" buttons, which are blunt instruments.

QueueHub

QueueHub supports the full BullMQ operation set on individual jobs (retry, promote from delayed, reprioritize, delete, rerun with modified data) plus filtered bulk operations:

• Retry all failed jobs matching a data filter.
• Delete all completed jobs older than N days.
• Promote all delayed jobs in a queue.
• Reprioritize jobs matching an error pattern.

All bulk operations are atomic and audit-logged.

Deployment Comparison

Arena deployment

Arena is a self-hosted process. Typical deployment looks like:

1. Clone the repo (or use the community Docker image).
2. Author the JSON config with your Redis connection details.
3. Run it behind a reverse proxy with TLS.
4. Layer auth in front (basic auth at minimum; ideally an OAuth proxy).
5. Supervise it with systemd / your container orchestrator.
6. Keep it patched and updated.

For a single team, this is an afternoon's work. For multiple environments (dev, staging, prod) and multiple teams, it multiplies.

QueueHub deployment

QueueHub has no deployment step on your side:

1. Create a workspace.
2. Add your Redis source (via outbound tunnel).
3. Invite your team.

That's it. There's no process to supervise, no reverse proxy to configure, no auth layer to bolt on.

Maintenance Status: A Critical Factor

Arena's biggest liability in 2026 is its maintenance status. The repository is not abandoned in the formal sense — it still receives occasional commits — but the cadence is slow enough that:

• Bug reports can sit unresolved for months.
• New BullMQ releases sometimes break Arena without an immediate fix.
• Security vulnerabilities in dependencies may not be promptly patched.
• Feature requests for modern BullMQ capabilities (flows, parent/child relationships, rate limiters) go unimplemented.

If you're choosing a tool to depend on for production monitoring, this matters. A dashboard that breaks on a BullMQ upgrade and takes weeks to fix is worse than no dashboard — it gives you false confidence.

QueueHub, as a commercial SaaS, has a funded team maintaining it. BullMQ compatibility is tracked against upstream releases, and updates ship continuously without any action on your part.

Security Considerations

Arena runs as an open web server with no built-in auth. In a production deployment, you must:

• Put it behind a firewall or VPN.
• Add authentication (basic auth, OAuth proxy, mTLS).
• Restrict which Redis operations it can perform (Arena needs fairly broad access).
• Keep its dependencies patched.

QueueHub's tunnel model means your Redis is never exposed to the internet — the tunnel is outbound-only. Authentication is handled by QueueHub (SSO, RBAC), and every job operation is audit-logged.

When to Choose Which

Choose Arena if:

• You want a completely free, self-hosted option and have the bandwidth to maintain it.
• Your team is small and the lack of auth/RBAC is acceptable (e.g., behind a VPN).
• You only need BullMQ and basic job operations.
• You're willing to accept slow upstream maintenance.

Choose QueueHub if:

• You want a modern, real-time UI for daily use.
• You need multi-backend support (BullMQ + BeeQueue + SQS).
• You need SSO, RBAC, and an audit log for a team.
• You want metrics (throughput, latency, failure rate) without building Grafana dashboards.
• You'd rather not own the deployment, supervision, and patching of a queue UI.

Migration From Arena to QueueHub

Moving from Arena to QueueHub is low-risk:

1. Create a QueueHub workspace and invite your team.
2. Add the same Redis sources Arena was configured to use.
3. Authorize the outbound tunnel — no inbound ports required.
4. Verify queues appear in the QueueHub dashboard.
5. Configure roles and SSO as appropriate.
6. Decommission Arena once you've validated the switch.

There's no data migration — both tools read directly from your Redis. You can run Arena and QueueHub in parallel during the transition.

Frequently Asked Questions

Is Arena still maintained?

Arena receives occasional commits but has a slow maintenance cadence. Bug fixes and support for new BullMQ features can lag significantly behind upstream.

Is Arena free?

Yes. Arena is open source and free to use, including commercially.

Can QueueHub replace Arena entirely?

For most teams, yes. QueueHub covers everything Arena does (BullMQ queue view, job inspection, retry/remove) and adds multi-backend support, real-time updates, metrics, SSO, RBAC, and audit logging.

Does QueueHub work with Redis behind a firewall?

Yes. QueueHub uses an outbound tunnel, so your Redis does not need to be reachable from the internet.

Conclusion

Arena deserves credit for being an early BullMQ UI when nothing else existed. But its minimal maintenance, dated UI, single-backend scope, and lack of auth make it a hard recommendation for production use in 2026.

QueueHub is built for the modern queue landscape: multi-backend, team-first, real-time, and actively maintained. If you're starting fresh or re-evaluating your queue dashboard, try QueueHub free.