QueueScope
Native macOS · Open source · v0.6.0

A native dashboard
for BullMQ.

Your BullMQ queues, without another dashboard to deploy. Group related failures, inspect the job behind them, and connect to private Redis—all from your Mac.

Free · macOS 14+ · Apple Silicon & Intel · Signed and notarized

No account requiredCredentials in KeychainNode runtime includedMIT licensed

A shorter path to an answer

Find failures.
Inspect the jobs behind them.

Explore a three-step walkthrough with light-mode app showcases and offline sample data.

Three failure groups in the offline demo.

Group related failures across queues, with scan coverage and timestamps for context.

Private Redis.
Within reach.

Connect through SSH with your existing keys or agent. Keep known-host checks and Redis TLS verification intact.

Feels at home on your Mac.

Native controls, local connections, and light and dark appearances. No dashboard service to run.

Read-only profiles

Look before you act.

Inspect payloads and state first. Use BullMQ-backed job actions when you're ready.

Ready when your queues aren’t

One app.
No extra runtime.

Download the ZIP, move QueueScope to Applications, and connect. Updates are available from the app menu.

Download QueueScope 0.6.0 ↓

macOS 14 or later · BullMQ 5.77.x

Try the offline demo or connect your first queue →

Prefer Homebrew?
brew install --cask raynirola/tap/queuescope

Our own tap. Same signed and notarized app.

View the cask ↗

From a symptom to the evidence

Debug your BullMQ queues.

Start with the problem in front of you. These guides explain what to inspect and where the dashboard’s view has limits.

Why did this job fail?

Group related errors, inspect payloads and stack traces, and check attempts before retrying.

Connect to private Redis through SSH · All articles and guides

Questions, answered.

Is QueueScope free?

Yes. QueueScope is free and open source under the MIT license. The signed Mac app is available from GitHub Releases or our Homebrew tap. No QueueScope account is required.

Which operating systems and BullMQ versions are supported?

QueueScope 0.6.0 requires macOS 14 or later and runs on Apple Silicon and Intel Macs. It targets BullMQ 5.77.x Redis layouts. It is not a Windows or Linux app, and compatibility with every BullMQ version is not guaranteed.

Do I need to install Node or run a dashboard server?

No. The packaged app includes its Node runtime and the official BullMQ package for job actions. You connect from the Mac app to Redis. Building QueueScope from source still requires the build dependencies described in the repository.

Where are Redis credentials and queue data stored?

Release builds store Redis credentials in macOS Keychain. Connection metadata and metric snapshots are stored locally. QueueScope does not send queue payloads or Redis credentials to a QueueScope service. Development builds use a separate unencrypted credential store. See our privacy policy for website analytics and update-check details.

Can I connect to Redis on a private network?

Yes, through an SSH tunnel using system OpenSSH and an existing key or SSH agent. The Redis address must be reachable from the SSH server. QueueScope retains known-host checks and Redis TLS verification. Interactive SSH password prompts are not supported. Read the SSH connection guide.

Does a read-only profile prevent job changes?

It prevents QueueScope job mutations, including bulk actions and queue pause/resume. The setting applies to the connected session; editing the form does not change an active session. Use Redis ACLs when you need server-enforced permissions. A read-only profile does not change what other applications can do.

Read all questions and answers · Explore articles and guides

Looking for a Bull Board alternative?

Compare QueueScope’s native Mac workflow with Bull Board and Workbench, from setup and connections to shared browser access.

Compare BullMQ dashboards

Help shape what comes next

Built around real debugging.

Found a rough edge or missing feature? Tell us what you were trying to do. Please keep credentials and customer data out of public issues.

Share feedback ↗