RedBeat is a Celery Beat Scheduler that stores the scheduled tasks and runtime metadata in Redis.
Why RedBeat?
Dynamic live task creation and modification, without lengthy downtime
Externally manage tasks from any language with Redis bindings
Shared data store; Beat isn’t tied to a single drive or machine
Fast startup even with a large task count
Prevent accidentally running multiple Beat servers
For more background on the genesis of RedBeat see this blog post
Getting Started
Install with pip:
pip install celery-redbeatConfigure RedBeat settings in your Celery configuration file:
redbeat_redis_url = "redis://localhost:6379/1"Then specify the scheduler when running Celery Beat:
celery beat -A <celery_app_file_path>.<celery_app_instance_name> -S redbeat.RedBeatSchedulerIf using the embedded beat in a worker process (like in development), specify the scheduler like so:
celery worker --beat --scheduler redbeat.RedBeatScheduler ...RedBeat uses a distributed lock to prevent multiple instances running. To disable this feature, set:
redbeat_lock_key = NoneMore details available on Read the Docs
Development
RedBeat is available on GitHub
Once you have the source you can run the tests with make (recommended):
make setup make test
Or using pip directly:
pip install -r requirements-dev.txt python -m unittest discover tests
Optional: if you use mise to manage Python, it will read .mise.toml and install the pinned Python version. After that, still use make for tasks:
mise install make setup && make test
You can also quickly fire up a sample Beat instance with:
celery beat --config exampleconf
1 maintainer
Metadata
1 maintainer
Release files for celery-redbeat 2.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| celery_redbeat-2.4.2.tar.gz | 36.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| celery_redbeat-2.4.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 53.2 kB
Release files / celery_redbeat-2.4.2.tar.gz
| Download URL | celery_redbeat-2.4.2.tar.gz |
|---|---|
| Size | 36.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a590fef7ef39d7e4511174ce8bafe310e07ef6cdf84a240cd311946815bd90bb
|
|
BLAKE2b-256 checksum How to use checksums |
03139aefb6cb39266b28ab2b2a8f24382fd7d82399e20578c5ba2238e63c4445
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logRelease files / celery_redbeat-2.4.2-py2.py3-none-any.whl
| Download URL | celery_redbeat-2.4.2-py2.py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4124d221a798ad983df0874bfa0d2e9beca41ca9ef91e92d073770bb193da000
|
|
BLAKE2b-256 checksum How to use checksums |
113dbb4adef34e7691ebd2e80c1e8df1fb3f3bf43b388de714219ac6a580a4d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency log
