How z4j stacks up.
Flower covers Celery and RQ Dashboard covers RQ. z4j covers six engines and adds capability-aware actions, schedules, RBAC, an audit trail and redaction. Here is how we compare, honestly.
vs. Flower
Celery only Flower
The classic Celery viewer.
- Positioning
- Celery monitoring and remote control
- License
- BSD-3, open source
vs. RQ Dashboard
RQ only RQ Dashboard
The simple web view for RQ.
- Positioning
- Lightweight viewer with basic requeue
- License
- Open source
vs. Grafana + Prometheus
Any engine, via custom exporters Grafana + Prometheus
The DIY metrics approach. Great for SRE, wrong tool for task ops.
- Positioning
- Metrics and alerting, not task-level control
- License
- AGPL-3 (Grafana) + Apache-2 (Prometheus)
How we compare
One table, the whole field
A high-level capability row. Click any dashboard above for the deep dive.
| Capability | Flower | RQ Dashboard | Grafana + Prometheus | z4j |
|---|---|---|---|---|
| Engine coverage | Celery only | RQ only | Whatever you export yourself | 6 engines |
| Persistent history | Optional persistent mode with a local database file | Only what RQ keeps in Redis (TTL-bound) | - | Database-backed |
| Retry / cancel actions | Task revoke/terminate and worker controls through UI/API | Requeue failed only | None - read-only dashboards | Capability-aware per engine |
| RBAC / multi-user | Multiple basic-auth users and OAuth; different authorization model | Basic-auth or none | - | Built-in |
| Audit log | None | None | None | HMAC-chained |
| Historical trends | Task views and Prometheus integration | Point-in-time queue and job views | - | Built-in |
This is a summary. Each dashboard's page has the full capability matrix with honest trade-offs.
Still on one of these?
Install z4j alongside your existing dashboard. Run both for a week. Keep what you prefer.