celery-redbeat

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

RedBeat is a Celery Beat scheduler that persists scheduled tasks and runtime state in Redis instead of the local filesystem, enabling dynamic task management and multi-instance coordination.

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

pip install celery-redbeat

uv add celery-redbeat

poetry add celery-redbeat

Installing celery-redbeat

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.

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.RedBeatScheduler

Requires a running Redis instance and an existing Celery application configured with a broker.

Verify 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

Evidence: celery_redbeat-2.4.2-py2.py3-none-any.whl

Keywords: python, celery, beat, redis, scheduler

Tags

More Distributed Computing packages