# AS a dedicated process
uv run celery -A {{ project_name }} beat -l info
```

Note that if you run Celery Beat as a standalone process, you will need to ensure that the Celery worker is running separately. This is because Celery Beat is responsible for scheduling tasks while the worker executes them.

#### Production Setup

[Section titled “Production Setup”](#production-setup)

In production, you can run Celery Beat as a separate process. You must ensure that there is only ever one Celery Beat process running at a time to avoid multiple instances of the same task being scheduled.

It’s also important to note that you can not run Celery Beat in the same process as a worker that is using the `gevent` pool.

For more information, see the [Celery Beat documentation](https://docs.celeryq.dev/en/stable/userguide/periodic-tasks.html).