> ## Documentation Index
> Fetch the complete documentation index at: https://docs.celeryroot.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Celery Root

> Celery Root is a modern replacement for the unmaintained Celery Flower. Monitor workers, inspect tasks, and manage queues from one control plane.

<Columns cols={2}>
  <div>
    Celery Root is a multi-worker monitoring, management, and visualization tool for Celery. It ships with a Django-based UI, a lightweight event listener/collector, and helper utilities for inspecting queues, tasks, workers, and beat schedules.
  </div>

  <div>
    <img src="https://mintcdn.com/celeryroot/xw36GYBKE-eet9aH/images/big_swag_logo.png?fit=max&auto=format&n=xw36GYBKE-eet9aH&q=85&s=d5215d10b0ad151b8bb63a7f74205d4b" alt="Celery Root logo" width="1024" height="1024" data-path="images/big_swag_logo.png" />
  </div>
</Columns>

## What you get

* Task list with filtering, sorting, and full detail views.
* Task relation graph visualization (chains, groups, chords, maps).
* Worker fleet overview and per-worker drill-down.
* Broker queue inspection and purge actions.
* Beat schedule overview and editor.
* Pluggable storage (SQLite by default).
* Optional Prometheus and OpenTelemetry metrics exporters.
* Optional MCP server for safe read-only data access.

## Start here

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/guides/quickstart">
    Run the demo stack and open the UI.
  </Card>

  <Card title="Configure" icon="sliders" href="/guides/configuration">
    Enable or disable components and set database paths.
  </Card>

  <Card title="UI tour" icon="grid" href="/guides/ui">
    See where to manage tasks, workers, brokers, and beat.
  </Card>

  <Card title="CLI" icon="terminal" href="/reference/cli">
    Run Celery Root as a standalone service or a Celery subcommand.
  </Card>
</Columns>

## Architecture at a glance

The supervisor process launches a DB manager, event listeners per broker, optional metrics exporters, the web UI, and the MCP server. See the architecture overview for details.

<Card title="Architecture" icon="sitemap" href="/architecture/overview" />
