Skip to main content
Django + Celery . Self-hosted . Open source

Django Celery Dashboard

Run Celery inside a Django app and you have working background jobs. Run Celery with z4j and you also have a dashboard, persistent history, the task controls this adapter can execute safely, scheduler integration, RBAC with invitations, and a tamper-evident audit log. z4j is one container or one Python process; the agent is one pip extra in your existing Django venv.

This is the most common stack we see. Django + Celery + django-celery-beat already covers task execution and scheduling. z4j adds the operator layer on top: who retried what, why it failed last Tuesday, what is still queued, when did this schedule last fire. The z4j-django adapter auto-detects your Celery app from cookiecutter, ROOT_URLCONF, WSGI, or BASE_DIR layouts, so wiring is a single Z4J dict in settings.py.

Install z4j Django integration details Celery adapter details
install

Install z4j alongside Django + Celery

1. Install the brain

bash 
pip install z4j && z4j serve

First boot prints a setup URL to stderr. Open it, create the first admin, and mint a token + HMAC secret for this agent.

2. Add the agent to your Django venv

bash 
pip install z4j-django[celery]

3. Wire it into Django

python 
# settings.py
INSTALLED_APPS += ["z4j_django"]

Z4J = {
    "brain_url":   env("Z4J_BRAIN_URL"),
    "token":       env("Z4J_TOKEN"),
    "hmac_secret": env("Z4J_HMAC_SECRET"),
    "project_id":  env("Z4J_PROJECT_ID"),
    "agent_name":  env("Z4J_AGENT_NAME", default=None),
}
# That's it. No CELERY_APP, no Z4J_DEV_MODE, no dev_mode kwarg.
# Auto-detect checks the documented candidate layouts. Add CELERY_APP when
# none of those candidates resolves your application.

What you get

  • Persistent Celery task history in Postgres or SQLite
  • Adapter-advertised controls: submit_task, retry_task, cancel_task, bulk_retry, purge_queue, restart_worker, pool_grow / pool_shrink, add_consumer / cancel_consumer, rate_limit
  • Scheduler integration via celery beat; available controls depend on that scheduler adapter
  • RBAC with invitations and password reset
  • HMAC-chained tamper-evident audit log
  • Notifications: email, Slack, Telegram, webhook
License

z4j-django and z4j-celery are Apache 2.0. Importing them into your Django app does not affect your application's licensing. z4j is AGPL-3.0-or-later, isolated in its own process.

Celery actions exposed

What the dashboard can actually do

Native actions

  • submit_task
  • retry_task
  • cancel_task
  • bulk_retry
  • purge_queue
  • restart_worker
  • pool_grow / pool_shrink
  • add_consumer / cancel_consumer
  • rate_limit

Event capture

Signals (in-process) + broker-events monitoring (fanout). Auto-switches based on worker pool type.

Reconciliation

celery.result.AsyncResult, authoritative; covers every backend (redis, rpc, db, etc.).

other Django stacks

Django with a different engine

Django +

Django RQ Dashboard

Lightweight Redis queue, fully instrumented.
Django +

Django Dramatiq Dashboard

Middleware-driven Dramatiq observability.
Django +

Django Huey Dashboard

Lightweight Redis/SQLite queue, first-class.
Django +

Django arq Dashboard

Async Redis queue for FastAPI-era Python.
Django +

Django taskiq Dashboard

Broker-agnostic async task framework.
Celery on other frameworks

Same engine, different framework

+ Celery

Flask Celery Dashboard

Flask extension pattern. One line to install.
+ Celery

FastAPI Celery Dashboard

Lifespan-hook integration for async stacks.

Start using Django Celery Dashboard

Self-hosted, open source, no SaaS, no telemetry. z4j runs anywhere Python or Docker runs.

Install z4j Read the docs