Role
Enabled by default
Celery in the Django stack
This page explains what Celery means in the Django stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
Celery is enabled by default in instances created from the Django stack, but it is not treated as a core required service.
Base service
Python (Django)
Type
service
Delivery
Connect your repository
Stack fit
How Celery fits into this stack
Celery is enabled by default in instances created from the Django stack, but it is not treated as a core required service.
This stack service is based on Python (Django) and keeps the service-specific setup for Django in one place.
Celery is a derivative service of Python.
Version policy
Available versions include 3.14, 3.13, 3.12, 3.11, 3.10.
Delivery
Build from your repository
Celery can build directly from a repository connected to the Django stack.
Inclusion
Enabled by default: Yes
Required: No
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
This stack service does not define persistent volume sizes.
Technical details inherit from the parent service
Celery is a derivative service of Python. Configs, settings, cron schedules, actions, volumes, and related runtime details are listed on the parent service page.