z4j vs. RQ Dashboard

The simple web view for RQ.

Scope: RQ only
Positioning: Lightweight viewer with basic requeue
License: MIT, open source

RQ Dashboard upstream project

what RQ Dashboard does well

Credit where it's due

Zero setup beyond RQ itself - one pip install and a Flask app

Clean, unpretentious UI focused on RQ's primitives

Good enough for small projects that only use RQ

Supports requeue of failed jobs and queue emptying

capability matrix

z4j vs. RQ Dashboard, feature by feature

Capability	RQ Dashboard	z4j
Engine coverage	RQ only	Celery, RQ, Dramatiq, Huey, arq, taskiq
Persistent history	Only what RQ keeps in Redis (TTL-bound)	Postgres-backed, full retention
Retry / cancel actions	Requeue failed only	Retry, cancel, bulk-retry, requeue-DLQ
Multi-queue across projects	All queues on one Redis	Per-project scoping with RBAC
Schedule management	Not included (needs rq-scheduler separately)	Integrated via z4j-rqscheduler adapter
RBAC / multi-user	Basic-auth or none	Owner / Admin / Operator / Viewer
Audit log	None	HMAC-chained, tamper-evident
Historical trends	None	Success, failure, runtime over time
Visual DAG / workflow graph	None	Tidy-tree SVG layout
Secret redaction	Raw args visible	Recursive scrubber + per-task overrides
Real-time updates	Poll-based refresh	WebSocket with HMAC-signed frames

migration guide

Cut over from RQ Dashboard in a week (or a weekend)

1

Run both side-by-side

Both tools read from Redis. There is no conflict running them in parallel. Leave RQ Dashboard up while you validate z4j.
2

Install z4j-rq alongside your worker

The RQ adapter instruments job lifecycle without monkey-patching. Your existing workers keep running unchanged.
3

Point at the same Redis

z4j picks up the same queues, jobs, and workers RQ Dashboard shows. You gain persistent history from the moment z4j starts recording.
4

Switch off RQ Dashboard once z4j covers your workflow

Keep the docker-compose entry for emergency fallback. Most teams never re-enable it.

honest trade-offs

Where we don't win

RQ Dashboard is a much smaller tool than z4j. If you only use RQ and never need audit trails, bulk actions, or multi-project scoping, it is simpler to operate.

z4j's value grows with scale. A single developer on a single queue may not need it.

other comparisons