--- id: django-celery-results version: "2.6.0" license: BSD license_treatment: permissive maintenance: active --- # django-celery-results — Celery result backends for Django. License: permissive · Maintenance: active · Downloads: 4.0M/mo ## What it is and what it does django-celery-results is a Django integration layer that lets you store Celery asynchronous task results directly in your Django database or cache, rather than in a separate result backend like Redis or RabbitMQ. It defines a single TaskResult model that you can query like any other Django ORM model, making it easy to track task status, retrieve results, and build dashboards or monitoring tools around your async workload. The package is designed for Django projects that already use Celery for task scheduling and execution. By storing results in your existing database, you avoid the operational overhead of maintaining a separate result storage system, though this approach trades some performance for simplicity. It supports modern Django versions (3.2 through 5.2) and Python 3.8 and later. Use it for: - Store Celery task results in your Django database so you can query them via the ORM alongside other application data. - Build a task history or audit trail by querying the TaskResult model to see which tasks ran, when, and what they returned. - Simplify deployment by eliminating the need for a dedicated result backend service when you already have a database. - Monitor long-running async operations by checking task status directly from your Django admin or custom dashboards. ## Worth the install? AI-flagged interpretation of the facts above — verify before relying. Stores Celery task results in a Django database or cache backend, making task completion status and results queryable through the Django ORM. Yes, if you use Celery with Django and prefer to avoid a separate result backend service. The package is actively maintained, has no known vulnerabilities, and integrates cleanly with the Django ORM. Install friction is low. Be aware that database-backed result storage may have different performance characteristics than Redis or similar backends, and MySQL users should verify the task ID length configuration for their version. ## Install pip install django-celery-results uv add django-celery-results poetry add django-celery-results ## Installing django-celery-results Before you install: Low friction install with only two runtime dependencies (celery and Django). Actively maintained as of 2026-08-10 with recent releases; no known vulnerabilities. License in practice: BSD license is permissive; you can use, modify, and distribute this package with minimal restrictions in both open-source and commercial projects. Quickstart: pip install django-celery-results # In Django settings.py: INSTALLED_APPS = [ 'django_celery_results', # ... ] CELERY_RESULT_BACKEND = 'django-db' # Then run migrations: # python manage.py migrate django_celery_results # Query results: from django_celery_results.models import TaskResult result = TaskResult.objects.get(task_id='your-task-id') print(result.result) Requires Django and Celery to be installed and configured; you must run Django migrations for the django_celery_results app before storing results. Verify before relying: - Whether MySQL-specific configuration (DJANGO_CELERY_RESULTS_TASK_ID_MAX_LENGTH) is still required for current MySQL versions. - Performance characteristics when storing large volumes of task results or querying historical results. ## Package facts - License: BSD (permissive) - Python support: unspecified - Install friction: low - Maintenance: active - Downloads: 4.0M/month (top 5,000 on PyPI) - Known vulnerabilities: none known ## Tags celery task results storage, django celery result backend, celery orm database results, async task result persistence, celery django integration, task result tracking database, celery-integration, async-tasks, django-orm [View on SkillFed](https://skillfed.io/packages/django-celery-results) · [View on PyPI](https://pypi.org/project/django-celery-results/)