celery-bloom
A modern, real-time monitoring UI for Celery — a drop-in replacement for Celery Flower with a clean dark UI, WebSocket-powered live updates, and rich task inspection.
Features
- Real-time task stream via WebSocket (no page refresh needed)
- Task search and filtering by state
- Rich task detail drawer — args, kwargs, result, traceback
- Worker view with active, reserved, and registered tasks
- Revoke / terminate running tasks from the UI
- Trigger any registered task from the UI with custom args/kwargs
- Execution trace view — visualise chains and groups as a live DAG
- Single
uv tool install— no Node.js required at runtime
Screenshots
Tasks
Workers
Trigger Task
Quick start
uv tool install celery-bloom
celery-bloom --broker redis://localhost:6379/0
Open http://localhost:5556.
Options
celery-bloom --help
--broker Celery broker URL (default: redis://localhost:6379/0)
--result-backend Result backend URL (optional)
--host Bind host (default: 0.0.0.0)
--port Port (default: 5556)
--log-level Log level (default: info)
Try it with Docker
Spin up Redis, a Celery worker, beat scheduler, and celery-bloom in one command:
# Build the frontend first (one-time)
make ui-install && make ui-build
# Start everything
docker compose up
# In another terminal, send some example tasks
docker compose exec worker uv run python example/seed.py --count 30
Open http://localhost:5556 and watch tasks flow in live.
The example app (example/tasks.py) includes:
tasks.add— quick arithmetic, random delaytasks.slow_job— long-running task with progress updatestasks.flaky— randomly fails and retriestasks.process_batch— batch processingtasks.health_check— runs every 30s via beat
Development
# Install Python deps
uv sync
# Install and run frontend dev server (hot reload on :5173, proxies API to :5556)
make ui-install
make ui-dev
# In another terminal
uv run celery-bloom --broker redis://localhost:6379/0
# Production build — bundles frontend into celery_bloom/static/
make ui-build
# Lint + type check
make lint
Tech stack
| Layer | Tech |
|---|---|
| Backend | FastAPI + uvicorn + Celery events |
| Frontend | React 18 + TypeScript + Vite |
| Styling | Tailwind CSS |
| Charts | Recharts |
| Graph | React Flow (@xyflow/react) + dagre |
| Data | TanStack Query + WebSocket |
License
MIT
Metadata
Release files for celery-bloom 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| celery_bloom-0.1.0.tar.gz | 56.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| celery_bloom-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 328.7 kB
Release files / celery_bloom-0.1.0.tar.gz
| Download URL | celery_bloom-0.1.0.tar.gz |
|---|---|
| Size | 56.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8cc51fa5434a49a83f673fc75564eefe9982f89e26ece536467ffbdef7dbf496
|
|
BLAKE2b-256 checksum How to use checksums |
dea6eea930169bd40203310f11f1a773edc61a3594827515364920144cd4db71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 20, 2026.
Transparency logRelease files / celery_bloom-0.1.0-py3-none-any.whl
| Download URL | celery_bloom-0.1.0-py3-none-any.whl |
|---|---|
| Size | 272.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3b3eb74476ae4f9ea762b21309980ea7415857c9a31223cbf0011fa26337b12
|
|
BLAKE2b-256 checksum How to use checksums |
e54eb6bb77eaf23533391edff79c03034a65c446c991d5ff0b4aa7f6f9ded1d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 20, 2026.
Transparency logSecurity for celery-bloom 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for celery_bloom-0.1.0.tar.gz
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 May 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.