Durabull Documentation
Welcome to the Durabull docs - setup, self-hosting, workflows, and operational best practices in one clear path.
Durabull is an open-source BullMQ management platform for teams that need fast, safe queue operations.
You can use it to monitor queue health, inspect and retry jobs, manage scheduled jobs, visualize workers, and debug with structured logs.
Start Here
If you are new, follow this order:
Documentation Map
Start Here
- Product orientation: How to Use Durabull
- Runtime behavior and mode selection: Architecture and Modes
- Auth and org model: Authentication and Organizations
- Redis connection lifecycle: Connection Management
- Connection setup failures and fixes: Connection Troubleshooting
Self Hosting
- Setup decisions: Self Hosting Setup
- Step-by-step install: Installation
- Container deployment: Docker Image and Compose
- Runtime configuration: Environment Variables
- Security baseline: Security and Hardening
Using Durabull
- Queue health and control: Queues Dashboard, BullMQ Native Metrics, Queue Operations
- Job-level triage: Job Lifecycle and Debugging
- Schedulers and workers: Scheduled Jobs, Workers Topology
- Standards: Queue and Scheduled Job Naming Best Practices, Log Formatting and Highlighting
Operations and Reference
- Incident playbook: Troubleshooting
- API endpoint catalog: HTTP API Reference
Friendly Rule of Thumb
During incidents, follow this sequence:
- Verify mode and active connection.
- Check queue health.
- Drill into job logs and stacktraces.
- Confirm scheduler and worker state.
- Use destructive queue actions only with explicit confirmation.