I built bullstudio, a modern dashboard for BullMQ that you can run like Prisma Studio:

npx bullstudio -r <redis_url> → it starts a local web UI (default http://localhost:4000) and opens your browser.

Why I built it In BullMQ-heavy projects, I kept losing time answering the same questions: Which queues are unhealthy? What’s failing right now? Where is this flow stuck? I’d bounce between logs, Redis inspection, and ad-hoc scripts. I wanted a “start it in seconds” UI that’s easy to point at any environment.

What it does today

Overview: queue health + throughput/failure trends

Jobs: browse + filter/search, inspect payload/attempts/stack traces, retry failed jobs

Flows: interactive parent/child visualization with live state updates

Repo: https://github.com/emirce/bullstudio

What I’d love feedback on

What are your “must-have” ops features for BullMQ (stalled detection, worker liveness, read-only mode, alerts, etc.)?

Payload safety: what defaults do you expect (truncation, masking keys like password/token, etc.)?

For teams with many queues/environments: what makes a dashboard feel production-ready?

Happy to answer any questions or add missing features if there’s demand.