celery-redbeat
A Celery Beat Scheduler using Redis for persistent storage
Decision gist · record as of 2026-08-14
Yes. RedBeat is production-stable (Development Status 5), actively maintained, has no known vulnerabilities, and solves a real problem for teams running distributed Celery deployments. Install it if you need dynamic task scheduling or multi-instance Beat coordination; skip it if you're using a single Beat instance with a static task set.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires a running Redis instance and an existing Celery application configured with a broker.
- Low friction install with a pure-Python wheel.
- Actively maintained with a recent release (18 days ago) and steady commit activity.
License · maintenance · safety
Apache License, Version 2.0 (permissive) — Apache License 2.0 (permissive) — you can use, modify, and distribute RedBeat freely in commercial and private projects, with minimal restrictions.
last release 2026-07-27 (18 days) · last repo commit 2026-08-13 · 1,050 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 5,407,560 downloads/mo, #2,107 on PyPI
Alternatives
Verify before relying
pip install celery-redbeat
# In your Celery config:
redbeat_redis_url = "redis://localhost:6379/1"
# Run with:
celery beat -S redbeat.RedBeatScheduler- Whether RedBeat's distributed lock mechanism works reliably across all deployment topologies.
- Performance characteristics when managing very large numbers of scheduled tasks.
- Compatibility with specific Redis cluster or sentinel configurations.
What it is and what it does
RedBeat replaces Celery Beat's default file-based scheduler with a Redis-backed alternative, storing both task definitions and runtime metadata in Redis. This enables you to create, modify, and delete scheduled tasks dynamically without restarting Beat, and to run multiple Beat instances safely against a shared Redis store without accidentally executing duplicate tasks.
It's built on top of celery, redis, python-dateutil, and tenacity, and is designed for distributed systems where Beat needs to be decoupled from a single machine or process. The scheduler uses a distributed lock to coordinate multiple instances, and supports live task creation from any language with Redis bindings.
Use it for
- Run Celery Beat across multiple machines or containers with a shared task schedule stored in Redis.
- Dynamically add, modify, or remove scheduled tasks at runtime without restarting Beat.
- Manage periodic tasks from external systems or languages by writing directly to Redis.
- Scale Beat horizontally while preventing duplicate task execution across instances.
- Migrate from file-based scheduling to a distributed, fault-tolerant model.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
RedBeat is production-stable (Development Status 5), actively maintained, has no known vulnerabilities, and solves a real problem for teams running distributed Celery deployments. Install it if you need dynamic task scheduling or multi-instance Beat coordination; skip it if you're using a single Beat instance with a static task set.
Install
celery-redbeat on PyPI
Before you install
Low friction install with a pure-Python wheel. Actively maintained with a recent release (18 days ago) and steady commit activity. Requires redis, celery, python-dateutil, and tenacity as runtime dependencies.
Requires a running Redis instance and an existing Celery application configured with a broker.
License in practice
Apache License 2.0 (permissive) — you can use, modify, and distribute RedBeat freely in commercial and private projects, with minimal restrictions.
Quickstart
pip install celery-redbeat
# In your Celery config:
redbeat_redis_url = "redis://localhost:6379/1"
# Run with:
celery beat -S redbeat.RedBeatSchedulerVerify before relying
- Whether RedBeat's distributed lock mechanism works reliably across all deployment topologies.
- Performance characteristics when managing very large numbers of scheduled tasks.
- Compatibility with specific Redis cluster or sentinel configurations.
Package facts
| License | Apache License, Version 2.0 permissive |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesrediscelerypython-dateutiltenacity |
| Maintenance | Actively maintained 18 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 5,407,560 / month, #2,107 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableLicense :: OSI Approved :: Apache Software LicenseOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.9Programming Language :: Python :: Implementation :: CPythonTopic :: Software Development :: Object BrokeringTopic :: System :: Distributed Computing |
Evidence: celery_redbeat-2.4.2-py2.py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “celery beat scheduler redis”
- celery-redbeatRedBeat is a Celery Beat scheduler that persists scheduled tasks and…
- sqlalchemy-celery-beatProvides a SQLAlchemy-backed scheduler for Celery that stores…
- django-celery-beatStores Celery periodic task schedules in a Django database and…
Give your agent the search over MCP, or paste the wish link into any chat.
More Distributed Computing packages
gRPC Python is an HTTP/2-based RPC framework that enables you to define and call remote procedures across network boundaries using protocol buffers for serialization.
Install it if you need RPC communication in a distributed system or are integrating with existing gRPC services.
execnet lets you spawn and communicate with Python interpreters across local processes, remote hosts, and different platforms, using a simple API for task distribution and inter-process messaging.
However, the aging maintenance status (275 days since last release) means you should verify it meets your concurrency and performance needs before committing to a…
Cloudpickle extends Python's standard pickle module to serialize lambda functions, interactively-defined functions and classes, and other constructs that the default pickle cannot handle, making it suitable for cluster computing and remote code execution.
Install it if you need to serialize lambda functions, interactively-defined code, or non-standard Python constructs for cluster computing or distributed execution.
Provides a unified, open()-compatible Python API for streaming large files from remote storage (S3, GCS, Azure, HDFS, SFTP, HTTP) and local filesystems, with transparent compression support.
Install it if you work with large files on cloud storage or remote systems and want to avoid writing boilerplate around multiple SDKs.
Portalocker provides cross-platform file locking with support for exclusive and shared locks, plus Redis-based distributed locks and process-aware PID file locking.
Install it if you need file or process coordination; the optional extras (pywin32, redis) are only required for specific lock types.
Ray is a distributed computing framework that scales Python applications from a single machine to multi-node clusters, providing abstractions for parallel tasks, stateful actors, and shared objects.
See also sqlalchemy-celery-beat · django-celery-beat · celery_once · celery-singleton · arq · rq-scheduler · celery · tenant-schemas-celery · pydocket · flower