Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

<@ULVA73B9P> when I run this command, which services is this disabling exactly? "prefect server start --host 0.0.0.0 --port 4200 --no-services"

:white_check_mark: thought for 189.4 seconds

Short answer: `--no-services` starts only the API/webserver (and the UI if `--ui` is enabled) and skips all background “loop services.”

In Prefect 3.x, the services this disables are the ones shown by `prefect server services list-services`. On my check, that includes:
- CancellationCleanup
- Foreman
- MarkLateRuns
- FailExpiredPauses
- RecentDeploymentsScheduler
- Scheduler
- TaskRunRecorder
- Telemetry
- EventLogger
- EventPersister
- ProactiveTriggers
- ReactiveTriggers
- Actions
- Distributor

Notes:
- You can see your exact list with:
  ```
  prefect server services list-services
  ```
- Some services have dedicated flags on `prefect server start`:
  - Scheduler: `--no-scheduler`
  - Late runs: `--no-late-runs`
  - Analytics/telemetry: `--analytics-off`
  - UI: `--no-ui` (UI isn’t part of “services” and can be toggled separately)
- Other services are controlled by environment variables (e.g., `PREFECT_SERVER_SERVICES_*_ENABLED`) but are all bypassed when you use `--no-services`.

Docs:
- <https://docs-3.prefect.io/v3/api-ref/cli/server|Prefect server CLI (start, services, etc.)>